From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] LTO: fallback to -flto=N if -flto=jobserver does not work.
Date: Thu, 22 Apr 2021 13:19:45 +0200 [thread overview]
Message-ID: <CAFiYyc0MJ6Cg4YZ+41g0O1-E69GKP3XhKbPe4rr03mtYfiqfDg@mail.gmail.com> (raw)
In-Reply-To: <8cc12cd9-fe88-f97b-eec2-d47f5342496d@suse.cz>
On Thu, Apr 22, 2021 at 11:02 AM Martin Liška <mliska@suse.cz> wrote:
>
> On 4/22/21 10:04 AM, Richard Biener wrote:
> > On Wed, Apr 21, 2021 at 3:08 PM Martin Liška <mliska@suse.cz> wrote:
> >>
> >> When -flto=jobserver is used and we cannot detect job server, then we can
> >> still fallbackto -flto=N mode.
> >>
> >> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
> >>
> >> Ready to be installed?
> >
> > I think this behavior needs to be documented - it falls back to a less
> > conservative (possibly system overloading) mode - which IMHO is
> > non-obvious and IMHO we shouldn't do.
>
> Sure, I'm sending corresponding patch. Note that it's quite common mistake
> that '+' is missing in Makefile rule. That was motivation for my change.
Sure, but that change won't get this fixed. IMHO we should eventually
emit diagnostic like
warning: could not find jobserver, compiling N jobs serially
once N > 1 (or 2?). Likewise if people just use -flto and auto-detection
finds nothing:
warning: using serial compilation of N LTRANS jobs
note: refer to http://.... for how to use parallel compile
using the URL diagnostics to point to -flto=... documentation.
That is, teach users rather than second-guessing and eventually
blowing things up. IMHO only the jobserver mode is safe to
automatically use.
Richard.
> Martin
>
> >
> > Richard.
> >
> >> Thanks,
> >> Martin
> >>
> >> gcc/ChangeLog:
> >>
> >> * lto-wrapper.c (run_gcc): When -flto=jobserver is used, but the
> >> makeserver cannot be detected, then use -flto=N fallback.
> >> ---
> >> gcc/lto-wrapper.c | 3 ++-
> >> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/gcc/lto-wrapper.c b/gcc/lto-wrapper.c
> >> index 03a5922f8ea..0b626d7c811 100644
> >> --- a/gcc/lto-wrapper.c
> >> +++ b/gcc/lto-wrapper.c
> >> @@ -1585,8 +1585,9 @@ run_gcc (unsigned argc, char *argv[])
> >> if (jobserver && jobserver_error != NULL)
> >> {
> >> warning (0, jobserver_error);
> >> - parallel = 0;
> >> + /* Fall back to auto parallelism. */
> >> jobserver = 0;
> >> + auto_parallel = 1;
> >> }
> >> else if (!jobserver && jobserver_error == NULL)
> >> {
> >> --
> >> 2.31.1
> >>
>
next prev parent reply other threads:[~2021-04-22 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 11:50 Martin Liška
2021-04-21 15:11 ` Jeff Law
2021-04-22 8:04 ` Richard Biener
2021-04-22 9:02 ` Martin Liška
2021-04-22 11:19 ` Richard Biener [this message]
2021-04-22 12:21 ` Martin Liška
2021-04-22 12:47 ` Richard Biener
2021-04-22 14:30 ` Martin Liška
2021-05-12 9:10 ` Martin Liška
2021-05-12 9:21 ` Richard Biener
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=CAFiYyc0MJ6Cg4YZ+41g0O1-E69GKP3XhKbPe4rr03mtYfiqfDg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).