From: Diego Novillo <dnovillo@google.com>
To: Ollie Wild <aaw@google.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"Kenneth Zadeck" <zadeck@naturalbridge.com>,
"\"Doug Kwan (關振德)\"" <dougkwan@google.com>
Subject: Re: [lto] add direct-to-ELF serialization to lto1
Date: Thu, 26 Jun 2008 13:38:00 -0000 [thread overview]
Message-ID: <4863903B.2050409@google.com> (raw)
In-Reply-To: <65dd6fd50806251156l647c5bb7vd5fe28e19d76d459@mail.gmail.com>
On 6/25/08 2:56 PM, Ollie Wild wrote:
> 3) In response to feedback from Kenny, I've removed the LTO language
> hooks and replaced them with an lto_set_out_hooks function. This
> mirrors the lto_set_in_hooks methodology, making things more
> consistent.
I don't understand this. Why not use langhooks instead of using another
hook mechanism? It's the same thing, but it seems to me that it'd be
more natural to just use the langhooks harness that we already have.
Kenny, any particular reason for having another hook mechanism?
Going through the rest of the patch now.
Diego.
next prev parent reply other threads:[~2008-06-26 12:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 19:04 Ollie Wild
2008-06-26 13:38 ` Diego Novillo [this message]
2008-06-26 17:57 ` Ollie Wild
2008-06-26 18:40 ` Ollie Wild
2008-06-26 18:58 ` Diego Novillo
2008-06-26 18:30 ` Kenneth Zadeck
2008-06-26 19:06 ` Diego Novillo
2008-06-26 20:07 ` Tom Tromey
2008-06-27 22:37 ` Mark Mitchell
2008-06-26 22:10 ` Diego Novillo
2008-06-27 20:16 ` Ollie Wild
2008-06-27 20:54 ` Kenneth Zadeck
2008-06-27 21:45 ` Diego Novillo
2008-06-27 21:38 ` Diego Novillo
2008-06-27 22:15 ` Ollie Wild
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=4863903B.2050409@google.com \
--to=dnovillo@google.com \
--cc=aaw@google.com \
--cc=dougkwan@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=zadeck@naturalbridge.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).