From: cbergstrom@pathscale.com
To: Lei Zhang <gentoo-dev@lists.gentoo.org>, gentoo-dev@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-dev] New project: LLVM
Date: Fri, 19 Aug 2016 09:07:37 +0700 [thread overview]
Message-ID: <20160819020737.5419083.98443.119986@pathscale.com> (raw)
In-Reply-To: <CAOYuCc2+B2DDPDMpA0xWpGXxuZQJVKm=Rf8COrKdTNMRyyJCJQ@mail.gmail.com>
That seems a lot like what we've already done. I guess a GSOC student is working on the libcxxabi piece. The only advantage to using our runtime, libcxxrt, is performance and code size.
Original Message
From: Lei Zhang
Sent: Friday, August 19, 2016 06:34
To: gentoo-dev@lists.gentoo.org
Reply To: gentoo-dev@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-dev] New project: LLVM
2016-08-18 21:56 GMT+08:00 C Bergström <cbergstrom@pathscale.com>:
> @mgorny may be able to help with some of this and has quite a bit of
> experience building clang/llvm. Where I work we use a "wrapper" that
> helps coordinate a lot of the moving pieces.
>
> https://github.com/pathscale/llvm-suite/
>
> This may not be the perfect "gentoo" way to handle it, but the
> approach would produce a clean and correct compiler. With llvm
> dependencies getting more and more complicated, I'm not sure if it
> would be possible to have both a gnu-free and also perfect
> 1-project-source-repo:1-ebuild ratio.
Currently the ebuilds for libunwind, libc++abi and libc++ all involve
some hackery to support standalone build. And the package clang is
just a placeholder, while it's actually built in llvm.
Maybe we can put them all into the llvm package, and control what
components to build via USE flags.
Lei
next prev parent reply other threads:[~2016-08-19 2:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 16:22 [gentoo-dev] New project: LLVM Michał Górny
2016-08-18 13:48 ` Ian Bloss
2016-08-18 13:56 ` C Bergström
2016-08-18 23:33 ` Lei Zhang
2016-08-19 2:07 ` cbergstrom [this message]
2016-08-19 2:40 ` Lei Zhang
2016-08-19 3:11 ` C Bergström
2016-08-19 15:01 ` Luca Barbato
2016-08-19 15:15 ` C Bergström
2016-08-19 17:38 ` Luca Barbato
2016-08-19 18:02 ` james
2016-08-19 18:20 ` C Bergström
2016-08-19 20:52 ` james
2016-08-19 21:05 ` C Bergström
2016-08-19 21:41 ` james
2016-08-20 5:45 ` C Bergström
2016-08-19 16:54 ` Lei Zhang
2016-08-19 17:13 ` C Bergström
2016-08-19 17:34 ` Luca Barbato
2016-08-21 1:10 ` Lei Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160819020737.5419083.98443.119986@pathscale.com \
--to=cbergstrom@pathscale.com \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox