public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/106624] [13 Regression] LTO plugin fails to build in parallel builds: xgcc: fatal error: cannot execute '/build/build/./prev-gcc/collect2': execv: Bad address Date: Mon, 15 Aug 2022 20:26:30 +0000 [thread overview] Message-ID: <bug-106624-4-HVj4Gneu7n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106624-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106624 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |ASSIGNED Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org --- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to Sergei Trofimovich from comment #4) > Bisected locally down to: > > 53e3b2bf16a486c15c20991c6095f7be09012b55 is the first bad commit > commit 53e3b2bf16a486c15c20991c6095f7be09012b55 > Author: Martin Liska <mliska@suse.cz> > Date: Tue Aug 9 13:59:36 2022 +0200 > > lto: support --jobserver-style=fifo for recent GNU make > > gcc/ChangeLog: > > * opts-jobserver.h: Add one member. > * opts-common.cc (jobserver_info::jobserver_info): Parse FIFO > format of --jobserver-auth. > > gcc/opts-common.cc | 17 +++++++++++++++-- > gcc/opts-jobserver.h | 2 ++ > 2 files changed, 17 insertions(+), 2 deletions(-) Funny. > > Which makes some sense as I locally run GNU make with --shuffle enabled by > default: https://savannah.gnu.org/bugs/index.php?62100 Well, it's more likely caused by the fact that recent GNU make uses of the newly added fifo style for jobserver. Let me try reproducing it with the current make master. > > It should generate environment something like 'MAKEFLAGS= -j2 > --jobserver-auth=3,4 --shuffle=1660054175'.
next prev parent reply other threads:[~2022-08-15 20:26 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-15 12:14 [Bug bootstrap/106624] New: " slyfox at gcc dot gnu.org 2022-08-15 12:14 ` [Bug bootstrap/106624] " slyfox at gcc dot gnu.org 2022-08-15 13:26 ` slyfox at gcc dot gnu.org 2022-08-15 13:47 ` marxin at gcc dot gnu.org 2022-08-15 19:50 ` slyfox at gcc dot gnu.org 2022-08-15 20:26 ` marxin at gcc dot gnu.org [this message] 2022-08-15 21:01 ` [Bug bootstrap/106624] [13 Regression] LTO plugin fails to build in parallel builds: xgcc: fatal error: cannot execute '/build/build/./prev-gcc/collect2': execv: Bad address since r13-2011-g53e3b2bf16a486 marxin at gcc dot gnu.org 2022-08-16 6:02 ` slyfox at gcc dot gnu.org 2022-08-16 7:58 ` rguenth at gcc dot gnu.org 2022-08-16 11:05 ` slyfox at gcc dot gnu.org 2022-08-16 11:27 ` marxin at gcc dot gnu.org 2022-08-16 11:50 ` [Bug driver/106624] " slyfox at gcc dot gnu.org 2022-08-16 12:16 ` cvs-commit at gcc dot gnu.org 2022-08-16 12:17 ` slyfox at gcc dot gnu.org 2023-01-24 10:52 ` cvs-commit at gcc dot gnu.org 2023-01-24 10:53 ` cvs-commit at gcc dot gnu.org 2023-01-24 10:55 ` cvs-commit at gcc dot gnu.org
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-106624-4-HVj4Gneu7n@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).