From: Richard Guenther <richard.guenther@gmail.com>
To: Diego Novillo <dnovillo@google.com>
Cc: Richard Guenther <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Jan Hubicka <jh@suse.de>
Subject: Re: [PATCH][2/n] LTO option handling/merging rewrite
Date: Sun, 30 Oct 2011 22:30:00 -0000 [thread overview]
Message-ID: <CAFiYyc3Oq4px_fq+c0OZRgetf77_pzdHj0HRcek5-g-cvbovqA@mail.gmail.com> (raw)
In-Reply-To: <CAD_=9DTp5Yv00WE=Vq2zczr4QjYL1-FT_2jQ4MQVJL4azXB80A@mail.gmail.com>
On Fri, Oct 28, 2011 at 4:48 PM, Diego Novillo <dnovillo@google.com> wrote:
> Isn't this the same patch as
> http://gcc.gnu.org/ml/gcc-patches/2011-10/msg02348.html?
No, it's updated to do exactly what we do now. Changes to behavior to be split
to 3/n (like warning about mismatches or fixing the way we handle fPIC).
Richard.
>
> Diego.
>
next prev parent reply other threads:[~2011-10-30 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 12:52 Richard Guenther
2011-10-28 15:20 ` Diego Novillo
2011-10-30 22:30 ` Richard Guenther [this message]
2011-10-28 15:56 ` Joseph S. Myers
2011-10-30 1:13 ` Richard Guenther
2011-10-30 19:01 ` Joseph S. Myers
2011-11-02 11:43 ` Richard Guenther
2023-01-17 9:46 ` Andreas Schwab
2011-10-28 15:59 ` Jack Howarth
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=CAFiYyc3Oq4px_fq+c0OZRgetf77_pzdHj0HRcek5-g-cvbovqA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.de \
--cc=rguenther@suse.de \
/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).