From: Chris Lattner <clattner@apple.com>
To: dberlin@dberlin.org
Cc: giovannibajo@libero.it, mark@codesourcery.com,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: Link-time optimzation
Date: Thu, 17 Nov 2005 00:52:00 -0000 [thread overview]
Message-ID: <6BF10211-4A56-46B3-8771-D691217961D7@apple.com> (raw)
Daniel Berlin Wrote:
> > It [LLVM] is proven to be stable, high-level enough to
> > perform any kind of needed optimization,
> This is not true, unfortunately. That's why it is called "low
level virtual machine".
> It doesn't have things we'd like to do high level optimizations
on, like
> dynamic_cast removal, etc.
For the record, this isn't really true at all. LLVM does already
capture some high-level program properties, and is constantly being
extended over time. I will note that it would be far easier to
extend LLVM with the functionality you desire than to reinvent a
whole new way of doing things.
That said, wanting to stay as close as possible to gimple is a
reasonable design point, and LLVM certainly isn't that.
-Chris
next reply other threads:[~2005-11-17 0:52 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 0:52 Chris Lattner [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-16 22:26 Mark Mitchell
2005-11-16 22:41 ` Andrew Pinski
2005-11-16 22:58 ` Andrew Pinski
2005-11-17 0:02 ` Andrew Pinski
2005-11-17 0:25 ` Andrew Pinski
2005-11-17 0:52 ` Tom Tromey
2005-11-17 0:26 ` Giovanni Bajo
2005-11-17 0:32 ` Daniel Berlin
2005-11-17 9:04 ` Giovanni Bajo
2005-11-17 16:25 ` Kenneth Zadeck
2005-11-17 1:20 ` Richard Henderson
2005-11-17 1:28 ` Mark Mitchell
2005-11-17 1:31 ` Daniel Jacobowitz
2005-11-17 3:35 ` Jeffrey A Law
2005-11-17 14:09 ` Daniel Berlin
2005-11-17 14:48 ` mathieu lacage
2005-11-17 11:41 ` Richard Earnshaw
2005-11-17 21:40 ` Ian Lance Taylor
2005-11-17 23:10 ` Robert Dewar
2005-11-17 23:42 ` Ian Lance Taylor
2005-11-18 2:13 ` Daniel Jacobowitz
2005-11-18 9:29 ` Bernd Schmidt
2005-11-18 11:19 ` Robert Dewar
2005-11-18 11:29 ` Richard Earnshaw
2005-11-18 18:35 ` Mike Stump
2005-11-18 2:33 ` Dale Johannesen
2005-11-18 3:11 ` Geert Bosch
2005-11-18 18:43 ` Mike Stump
2005-11-18 18:30 ` Mike Stump
2005-11-17 15:54 ` Kenneth Zadeck
2005-11-17 16:41 ` Jan Hubicka
2005-11-18 16:31 ` Michael Matz
2005-11-18 17:04 ` Steven Bosscher
2005-11-18 17:29 ` Michael Matz
2005-11-18 17:24 ` Nathan Sidwell
2005-11-17 1:43 ` Gabriel Dos Reis
2005-11-17 1:53 ` Andrew Pinski
2005-11-17 2:39 ` Kean Johnston
2005-11-17 5:53 ` Ian Lance Taylor
2005-11-17 13:08 ` Ulrich Weigand
2005-11-17 21:42 ` Ian Lance Taylor
2005-11-17 16:17 ` Kenneth Zadeck
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=6BF10211-4A56-46B3-8771-D691217961D7@apple.com \
--to=clattner@apple.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
--cc=mark@codesourcery.com \
/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).