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/96794] New: --with-build-config=bootstrap-lto-lean with --enable-link-mutex leads to poor LTRANS utilization Date: Wed, 26 Aug 2020 09:16:45 +0000 [thread overview] Message-ID: <bug-96794-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96794 Bug ID: 96794 Summary: --with-build-config=bootstrap-lto-lean with --enable-link-mutex leads to poor LTRANS utilization Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org Target Milestone: --- As seen here:https://gist.githubusercontent.com/marxin/223890df4d8d8e490b6b2918b77dacad/raw/7e0363da60dcddbfde4ab68fa3be755515166297/gcc-10-with-zstd.svg each blocking linking of a GCC front-end leads to a wasted jobserver worker.
next reply other threads:[~2020-08-26 9:16 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-26 9:16 marxin at gcc dot gnu.org [this message] 2020-08-26 9:17 ` [Bug bootstrap/96794] " marxin at gcc dot gnu.org 2020-08-26 9:49 ` [Bug bootstrap/96794] New: " Jan Hubicka 2020-08-26 9:49 ` [Bug bootstrap/96794] " hubicka at ucw dot cz 2020-08-26 9:56 ` marxin at gcc dot gnu.org 2020-08-26 10:04 ` Jan Hubicka 2020-08-26 10:04 ` hubicka at ucw dot cz 2020-08-26 10:13 ` marxin at gcc dot gnu.org 2020-08-26 10:14 ` Jan Hubicka 2020-08-26 10:14 ` hubicka at ucw dot cz 2020-08-26 10:40 ` rguenth at gcc dot gnu.org 2020-08-26 10:58 ` rguenther at suse dot de 2020-08-26 11:07 ` marxin at gcc dot gnu.org 2020-08-26 12:23 ` matz at gcc dot gnu.org 2020-08-26 12:35 ` hubicka at ucw dot cz 2020-08-26 13:02 ` matz at gcc dot gnu.org 2020-08-26 13:20 ` 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-96794-4@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).