public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/106328] Build doesn't respect -j N flag
Date: Wed, 10 Aug 2022 12:51:58 +0000 [thread overview]
Message-ID: <bug-106328-4-wXFg3QxSyZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106328-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106328
--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 10 Aug 2022, marxin at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106328
>
> --- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
> > Magically only with recent GNU make, otherwise needs proper prefixed
> > rules in the lto-wrapper generated makefile which I don't think we do.
>
> Wait, the cooperation works with older GNU make if a Makefile uses prefixed (+)
> rules. WPA does not email any artificial Makefile for WPA streaming. It's a
> Makefile we emit for LTRANS run, e.g.:
>
> marxin@marxinbox:/dev/shm/objdir> cat /tmp/ccuhgkQs.mk
> ./a.ltrans0.ltrans.o:
> @g++ '-xlto' '-c' '-fno-openmp' '-fno-openacc' '-fno-pie'
> '-fcf-protection=none' '-mtune=generic' '-march=x86-64' '-O2' '-save-temps'
> '-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64' '-dumpdir' 'a.'
> '-dumpbase' './a.ltrans0.ltrans' '-fltrans' '-o' './a.ltrans0.ltrans.o'
> './a.ltrans0.o'
> ./a.ltrans1.ltrans.o:
> @g++ '-xlto' '-c' '-fno-openmp' '-fno-openacc' '-fno-pie'
> '-fcf-protection=none' '-mtune=generic' '-march=x86-64' '-O2' '-save-temps'
> '-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64' '-dumpdir' 'a.'
> '-dumpbase' './a.ltrans1.ltrans' '-fltrans' '-o' './a.ltrans1.ltrans.o'
> './a.ltrans1.o'
> ...
>
> So what can be miss is jobserver detection on BSD that can fail for some
> reason, but it should work fine apart from that. Or do I miss something?
Ah, indeed. That still leaves the question whether we execute the
WPA stage with the FDs open - I suppose you checked? And whether
pex_* "properly" does this for all host OSs (how does make jobserver
work on mingw/cygwin?). I wonder because Honza once said he didn't
implement jobserver support because it would require more fiddling
to get it actually work.
And IIRC BSD 'make' is not GNU make but I think gmake is available
from the ports repo. The documentation about -flto=jobserver mentions
that already.
prev parent reply other threads:[~2022-08-10 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 20:15 [Bug other/106328] New: " yuri at tsoft dot com
2022-07-17 19:47 ` [Bug lto/106328] " pinskia at gcc dot gnu.org
2022-07-18 7:55 ` rguenth at gcc dot gnu.org
2022-07-18 7:59 ` rguenth at gcc dot gnu.org
2022-07-18 8:03 ` rguenth at gcc dot gnu.org
2022-08-04 13:13 ` marxin at gcc dot gnu.org
2022-08-10 11:56 ` cvs-commit at gcc dot gnu.org
2022-08-10 11:56 ` marxin at gcc dot gnu.org
2022-08-10 12:40 ` rguenther at suse dot de
2022-08-10 12:46 ` marxin at gcc dot gnu.org
2022-08-10 12:51 ` rguenther at suse dot de [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=bug-106328-4-wXFg3QxSyZ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).