public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Wed, 10 Aug 2022 11:56:05 +0000 [thread overview] Message-ID: <bug-106328-4-R4H0d4diVJ@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 #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:fed766af32ed6cd371016cc24e931131e19b4eb1 commit r13-2012-gfed766af32ed6cd371016cc24e931131e19b4eb1 Author: Martin Liska <mliska@suse.cz> Date: Tue Aug 9 13:59:39 2022 +0200 lto: respect jobserver in parallel WPA streaming PR lto/106328 gcc/ChangeLog: * opts-jobserver.h (struct jobserver_info): Add pipefd. (jobserver_info::connect): New. (jobserver_info::disconnect): Likewise. (jobserver_info::get_token): Likewise. (jobserver_info::return_token): Likewise. * opts-common.cc: Implement the new functions. gcc/lto/ChangeLog: * lto.cc (wait_for_child): Decrement nruns once a process finishes. (stream_out_partitions): Use job server if active. (do_whole_program_analysis): Likewise.
next prev parent reply other threads:[~2022-08-10 11:56 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 [this message] 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-R4H0d4diVJ@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).