From: Diego Novillo <dnovillo@google.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches@gcc.gnu.org, rguenther@suse.de
Subject: Re: Fix LTO parameter sharing
Date: Wed, 11 Nov 2009 20:50:00 -0000 [thread overview]
Message-ID: <b798aad50911111243j7b253444y5a8eb561f2316d7@mail.gmail.com> (raw)
In-Reply-To: <84fc9c000911111241n49b55ab3h74baff013c8362e7@mail.gmail.com>
On Wed, Nov 11, 2009 at 15:41, Richard Guenther
<richard.guenther@gmail.com> wrote:
> Indeed. I wrote the patch, so I probably cannot use the excuse that
> Honza posted it to circumvent my LTO reviewer status ;) But it's sort-of
> middle-end anyway ... (I "approved" it from the seat right next of Honza)
Ha ha. That's fine. I figured that something like that had happened,
but I'm bored, so... ;)
Diego.
prev parent reply other threads:[~2009-11-11 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 20:23 Jan Hubicka
2009-11-11 20:41 ` Diego Novillo
2009-11-11 20:42 ` Richard Guenther
2009-11-11 20:50 ` Diego Novillo [this message]
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=b798aad50911111243j7b253444y5a8eb561f2316d7@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rguenther@suse.de \
--cc=richard.guenther@gmail.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).