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/84402] [meta] GCC build system: parallelism bottleneck
Date: Wed, 30 Nov 2022 09:10:08 +0000 [thread overview]
Message-ID: <bug-84402-4-Wmq8xQ61ut@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-84402-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84402
--- Comment #53 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #50)
> (In reply to Martin Liška from comment #48)
> > Created attachment 53989 [details]
> > CPU utilization of make all-host on recent AMD server
> >
> > The situation with a recent AMD server is really bad! Having 192 cores, the
> > average CPU utilization of `make all-host` is 6% !
>
> Just do more builds in parallel!
No! I'm speaking about faster edit-build-debug cycles and also about faster
builds of gcc packages.
> There's just 903 .o files in gcc/ and
> libbackend.a just has 490 of them. It's not surprising the few larger
> files stretch out the compile-time here.
Well, gimple-match.o takes ~66s on my new AMD Ryzen 9 5950X CPU :/
> Try LTOing libbackend.a?
Yep, that's our parallel for free approach and I would welcome that, however:
during IPA pass: inline
In member function ‘quick_push’,
inlined from ‘make_forwarders_with_degenerate_phis’ at
/home/marxin/Programming/gcc/gcc/tree-ssa-dce.cc:1848:6:
/home/marxin/Programming/gcc/gcc/vec.h:1958:28: internal compiler error:
Segmentation fault
1958 | return m_vec->quick_push (obj);
| ^
0x102f987 internal_error(char const*, ...)
???:0
0x117935b cgraph_node::get_untransformed_body()
???:0
0x123f6e9 optimize_inline_calls(tree_node*)
???:0
0x123e4d2 inline_transform(cgraph_node*)
???:0
0x123da5f execute_all_ipa_transforms(bool)
???:0
0x15ebe1b cgraph_node::expand()
???:0
0x15e2f6d symbol_table::compile()
???:0
0x15d0368 lto_main()
???:0
I'll isolate that and hope we can add a configure option for LTOed
libbackend.a.
next prev parent reply other threads:[~2022-11-30 9:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-84402-4@http.gcc.gnu.org/bugzilla/>
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-05-07 22:59 ` egallager at gcc dot gnu.org
2020-07-09 9:44 ` rjiejie at me dot com
2020-07-09 10:04 ` marxin at gcc dot gnu.org
2020-07-09 11:40 ` rguenth at gcc dot gnu.org
2020-07-13 5:51 ` rjiejie at me dot com
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-07-19 6:17 ` pinskia at gcc dot gnu.org
2021-07-19 6:19 ` pinskia at gcc dot gnu.org
2021-10-09 12:58 ` egallager at gcc dot gnu.org
2021-10-11 8:01 ` marxin at gcc dot gnu.org
2021-10-11 18:10 ` egallager at gcc dot gnu.org
2021-11-01 4:56 ` egallager at gcc dot gnu.org
2022-05-29 3:44 ` sam at gentoo dot org
2022-06-02 22:05 ` segher at gcc dot gnu.org
2022-11-30 8:13 ` marxin at gcc dot gnu.org
2022-11-30 8:23 ` marxin at gcc dot gnu.org
2022-11-30 8:25 ` rguenth at gcc dot gnu.org
2022-11-30 8:27 ` rguenth at gcc dot gnu.org
2022-11-30 8:38 ` rguenth at gcc dot gnu.org
2022-11-30 9:10 ` marxin at gcc dot gnu.org [this message]
2022-12-01 9:43 ` marxin at gcc dot gnu.org
2022-12-01 10:01 ` marxin at gcc dot gnu.org
2022-12-01 10:03 ` marxin at gcc dot gnu.org
2022-12-01 10:07 ` marxin at gcc dot gnu.org
2023-03-27 14:55 ` andrew.carlotti at arm dot com
2023-03-28 3:01 ` marxin at gcc dot gnu.org
2023-03-28 8:30 ` rguenth at gcc dot gnu.org
2023-03-28 8:45 ` amonakov at gcc dot gnu.org
2023-03-28 8:54 ` jakub at gcc dot gnu.org
2023-03-28 9:05 ` rguenther at suse dot de
2023-03-28 11:31 ` cvs-commit at gcc dot gnu.org
2023-05-05 12:47 ` cvs-commit at gcc dot gnu.org
2023-05-05 12:47 ` cvs-commit at gcc dot gnu.org
2023-05-05 12:47 ` cvs-commit at gcc dot gnu.org
2023-05-05 12:48 ` cvs-commit at gcc dot gnu.org
2023-05-05 12:48 ` cvs-commit at gcc dot gnu.org
2023-05-05 12:48 ` cvs-commit at gcc dot gnu.org
2023-07-07 11:29 ` sjames at gcc dot gnu.org
2023-10-31 12:35 ` cvs-commit at gcc dot gnu.org
2023-10-31 12:48 ` sjames at gcc dot gnu.org
2024-03-04 4:29 ` law 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-84402-4-Wmq8xQ61ut@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).