public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/105747] Scheduler can take a long time on arm-linux sometimes
Date: Sun, 12 Jun 2022 09:40:17 +0000 [thread overview]
Message-ID: <bug-105747-4-utsgkzQU6y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105747-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105747
--- Comment #9 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to David Binderman from comment #8)
> (In reply to David Binderman from comment #7)
> > Created attachment 53119 [details]
> > C source code
> >
> > Another one. Over 15 minutes this time.
>
> Flag -O2 required.
Runs in 21 minutes on an RP3.
dcb@raspberrypi:~/csmith $ (ulimit -t 1800;time /home/dcb/gcc/results/bin/gcc
-I/home/dcb/csmith/results/include/csmith-2.3.0/
-c -g -w -O2 -freport-bug -ftime-report destDir/testFile.23139.c )
Time variable usr sys wall
GGC
phase parsing : 0.77 ( 0%) 1.55 ( 33%) 2.31 ( 0%)
3597k ( 2%)
phase opt and generate :1261.54 (100%) 3.05 ( 66%)1267.62 (100%)
188M ( 97%)
callgraph functions expansion :1212.97 ( 96%) 2.24 ( 48%)1218.13 ( 96%)
179M ( 93%)
callgraph ipa passes : 47.88 ( 4%) 0.79 ( 17%) 48.78 ( 4%)
4512k ( 2%)
alias stmt walking : 125.32 ( 10%) 0.70 ( 15%) 127.13 ( 10%)
126k ( 0%)
preprocessing : 0.20 ( 0%) 0.44 ( 9%) 0.58 ( 0%)
941k ( 0%)
lexical analysis : 0.25 ( 0%) 0.47 ( 10%) 0.87 ( 0%)
0 ( 0%)
parser function body : 0.23 ( 0%) 0.49 ( 11%) 0.68 ( 0%)
1585k ( 1%)
tree operand scan : 0.31 ( 0%) 0.33 ( 7%) 0.71 ( 0%)
830k ( 0%)
tree SSA verifier : 3.12 ( 0%) 0.10 ( 2%) 3.12 ( 0%)
0 ( 0%)
dead store elim2 : 16.05 ( 1%) 0.13 ( 3%) 16.30 ( 1%)
62M ( 32%)
PRE : 19.65 ( 2%) 0.25 ( 5%) 19.90 ( 2%)
46M ( 24%)
scheduling : 865.21 ( 69%) 0.20 ( 4%) 867.61 ( 68%)
4186k ( 2%)
address taken : 0.16 ( 0%) 0.14 ( 3%) 0.22 ( 0%)
0 ( 0%)
Extra diagnostic checks enabled; compiler may run slowly.
Configure with --enable-checking=release to disable checks.
real 21m10.578s
user 21m2.776s
sys 0m4.705s
next prev parent reply other threads:[~2022-06-12 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:49 [Bug c/105747] New: Possible resource hog with -O2 -fno-var-tracking dcb314 at hotmail dot com
2022-05-27 9:14 ` [Bug middle-end/105747] " pinskia at gcc dot gnu.org
2022-05-27 9:22 ` dcb314 at hotmail dot com
2022-05-27 9:31 ` [Bug rtl-optimization/105747] Scheduler can take a long time on arm-linux sometimes pinskia at gcc dot gnu.org
2022-05-27 11:14 ` rguenth at gcc dot gnu.org
2022-06-07 8:28 ` dcb314 at hotmail dot com
2022-06-07 9:30 ` dcb314 at hotmail dot com
2022-06-11 9:45 ` dcb314 at hotmail dot com
2022-06-11 9:48 ` dcb314 at hotmail dot com
2022-06-12 9:40 ` dcb314 at hotmail dot com [this message]
2024-02-19 13:29 ` rguenth 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-105747-4-utsgkzQU6y@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).