From: Harvey Harrison <harvey.harrison@gmail.com>
To: Chris Lattner <clattner@apple.com>
Cc: Diego Novillo <dnovillo@google.com>, gcc@gcc.gnu.org
Subject: Re: [RFC] WHOPR - A whole program optimizer framework for GCC
Date: Thu, 13 Dec 2007 07:14:00 -0000 [thread overview]
Message-ID: <1197504667.21291.57.camel@brick> (raw)
In-Reply-To: <ADCB933E-28A0-4B0C-862F-9968C22DF16D@apple.com>
On Wed, 2007-12-12 at 16:02 -0800, Chris Lattner wrote:
> On Dec 12, 2007, at 3:41 PM, Harvey Harrison wrote:
> >> In terms of implementation, we will likely use the LTO branch as a
> >> basis. Many of the features we will need are already being
> >> implemented
> >> in the branch, so we will keep helping with that implementation.
> >>
> >
> > I'm curious how this interacts/complements with any efforts to
> > using the LLVM IR in LTO.
> >
> > Any pointers to where that discussion ended up?
>
> There are no plans to integrate LLVM with mainline GCC. LLVM
> maintains its own permanent fork of GCC, which we periodically sync
> up with GCC's progress (e.g. LLVM 2.2 will include a GCC 4.2 based
> front-end). There is also work underway to build llvm-native front-
> end technology (http://clang.llvm.org).
>
> If you want LTO today, feel free to go to http://llvm.org/ :)
> otherwise LLVM is irrelevant to this discussion.
I was more interested in the format of the IR gcc ends up using, I was
curious where the discussion had gotten for LTO in gcc-land. The LLVM
representation seemed rather sane, and already has at least one
implementation of tools using it.
Harvey
next prev parent reply other threads:[~2007-12-13 0:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 20:54 Diego Novillo
2007-12-12 23:32 ` Tim Josling
2007-12-13 7:53 ` Ollie Wild
2007-12-13 14:09 ` Diego Novillo
2007-12-19 22:29 ` Tim Josling
2007-12-19 22:29 ` Diego Novillo
2007-12-19 22:34 ` Chris Lattner
2007-12-19 22:49 ` Diego Novillo
2007-12-13 0:03 ` Harvey Harrison
2007-12-13 0:11 ` Chris Lattner
2007-12-13 7:14 ` Harvey Harrison [this message]
2007-12-13 14:41 ` Diego Novillo
2007-12-13 19:06 ` Chris Lattner
2007-12-13 7:32 ` Praveen Raghavan
2007-12-13 8:10 ` Ollie Wild
2007-12-18 13:48 ` Jan Hubicka
2007-12-19 17:22 ` Diego Novillo
2007-12-19 18:55 ` Kenneth Zadeck
2007-12-20 3:48 ` Diego Novillo
2007-12-20 4:59 ` Kenneth Zadeck
2007-12-20 8:53 ` Jan Hubicka
2007-12-12 21:15 J.C. Pizarro
2007-12-12 22:42 ` Jonathan Wakely
2007-12-12 22:42 ` J.C. Pizarro
2007-12-12 22:50 ` Daniel Jacobowitz
2007-12-12 23:29 ` Sebastian Pop
2007-12-13 10:22 ` Paolo Bonzini
2007-12-13 13:32 ` Nicholas Nethercote
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=1197504667.21291.57.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=clattner@apple.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).