From: Richard Biener <richard.guenther@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Martin Sebor <msebor@redhat.com>
Subject: Re: [patch] update function comments for lto_symtab_encoder_encode_*
Date: Thu, 15 Jan 2015 09:39:00 -0000 [thread overview]
Message-ID: <CAFiYyc1haGs_YwUeJXE3ubxCZSDFD35-AExJTwDM8a1_Epq2-Q@mail.gmail.com> (raw)
In-Reply-To: <54B6A01A.5040709@redhat.com>
On Wed, Jan 14, 2015 at 5:58 PM, Aldy Hernandez <aldyh@redhat.com> wrote:
> On 01/14/2015 01:06 AM, Richard Biener wrote:
>
>>> Whenever I get to the LTO part of this project, I promise to start
>>> documenting things better. This whole thing is a mystery.
>>
>>
>> Well - mostly to me as well ;) I'll let Honza answer this...
>
>
> Ha, you're being too modest! I get the feeling that no one wants to own up
> to LTO :).
>
> So...
>
> Would anyone mind if I removed all references of "WHOPR" in the
> documentation (doc/lto.texi) and in *most* of the comments in the source?
> AFAICT, WHOPR has been the default LTO mode since Richard's linker plugin
> patch here:
>
> https://gcc.gnu.org/ml/gcc-patches/2014-03/msg00157.html
>
> From what I can see, WHOPR is the default unless no partitions were found,
> but otherwise there is no way to disable it. It's just confusing to have
> this nomenclature that is mostly not applicable.
You can disable WHOPR with -flto-partition=none, otherwise partitions
are always "found" (thus even if we identify only a single partition
we use a separate ltrans process).
> I obviously wouldn't change actual code, since we're past stage1, but
> comments/documentation are fair game. Eventually, I'd like to change the
> code to something like "LTO partitioning mode" or something (at the next
> stage1).
>
> Would this be acceptable?
I'm not sure what you propose to change? The references to "WHOPR"
may be historical (refering to the design document), and re-wording
the user-level and internals documentation to make it the default behavior
and maybe cite non-whopr mode as optimization in case of a single
partition is ok.
Note that we still have the issue that we want to exercise both
WHOPR and non-WHOPR in the testsuite but all testcases are so
small that we'd automagically would use non-WHOPR mode (if
such automatism was implemented...).
Richard.
> Aldy
next prev parent reply other threads:[~2015-01-15 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 16:38 Aldy Hernandez
2015-01-14 9:18 ` Richard Biener
2015-01-14 18:28 ` Aldy Hernandez
2015-01-15 9:39 ` Richard Biener [this message]
2015-01-16 12:35 ` Ilya Verbin
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=CAFiYyc1haGs_YwUeJXE3ubxCZSDFD35-AExJTwDM8a1_Epq2-Q@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=msebor@redhat.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).