public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rjiejie at me dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/84402] [meta] GCC build system: parallelism bottleneck
Date: Mon, 13 Jul 2020 05:51:49 +0000 [thread overview]
Message-ID: <bug-84402-4-FuySnE0rLg@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 #38 from jojo <rjiejie at me dot com> ---
(In reply to Martin Liška from comment #36)
> (In reply to jojo from comment #35)
> > (In reply to Martin Liška from comment #30)
> > > A possible solution can be usage of '-flinker-output=nolto-rel -r' for huge
> > > files.
> >
> > it's useful for splitting huge files ?
>
> There's experiment I did:
>
> $ time g++ -O2 /tmp/gimple-match.ii -c
>
> real 0m35.790s
> user 0m35.490s
> sys 0m0.268s
>
> $ time g++ -O2 /tmp/gimple-match.ii -c -flto
>
> real 0m8.138s
> user 0m7.915s
> sys 0m0.202s
>
> $ time gcc -flto=auto -flinker-output=nolto-rel gimple-match.o -r -o
> gimple-match2.o
>
> real 0m9.087s
> user 1m56.028s
> sys 0m3.292s
>
> $ time gcc -flto=auto -flinker-output=nolto-rel gimple-match.o -r -o
> gimple-match2.o --param lto-partitions=8
>
> real 0m7.350s
> user 0m48.548s
> sys 0m0.976s
>
> $ time gcc -flto=auto -flinker-output=nolto-rel gimple-match.o -r -o
> gimple-match2.o --param lto-partitions=4
>
> real 0m9.847s
> user 0m30.462s
> sys 0m0.392s
>
> so for N==4 we get to 8+10s = 18s (compared to the original 36s). And total
> user time is 30+8, which is comparable
> to the original 36s.
It's looks a little cost down for huge file as insn-emit.c......
I want to use shell tool like 'csplit' to split it and compile parallelly
next prev parent reply other threads:[~2020-07-13 5:51 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 [this message]
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
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-FuySnE0rLg@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).