public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/106328] Build doesn't respect -j N flag Date: Mon, 18 Jul 2022 07:55:20 +0000 [thread overview] Message-ID: <bug-106328-4-KgwqOEbq3e@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Keywords| |lto Last reconfirmed| |2022-07-18 Ever confirmed|0 |1 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- That's the WPA LTRANS file generation which does not use the jobserver but parallelizes for I/O. There is --param lto-max-streaming-parallelism you can use to limit things but it's default is 32 (but that would be per actual parallel invoked LTO link step, so with -j8 it's 8 * 32 when there are 8 parallel invoked link steps). See gcc/lto/lto.{c,cc}:stream_out_partitions which indeed says #ifdef HAVE_WORKING_FORK ... /* Do not run more than LTO_PARALLELISM streamings FIXME: we ignore limits on jobserver. */ if (lto_parallelism > 0 && nruns >= lto_parallelism) { wait_for_child (); ... if (!cpid) { setproctitle ("lto1-wpa-streaming"); so "confirmed" - it doesn't honor the jobserver. Note without using -flto=auto or -flto=jobserver it would be all serial, note the above also does not honor a limit placed via -flto=8 I think.
next prev parent reply other threads:[~2022-07-18 7:55 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 [this message] 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
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-KgwqOEbq3e@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: linkBe 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).