public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/109983] [12/13/14 regression] Wireshark compilation hangs with -O2 -fipa-pta
Date: Fri, 26 May 2023 18:17:54 +0000 [thread overview]
Message-ID: <bug-109983-4-SZbDzEMpbg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109983-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109983
--- Comment #6 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
Created attachment 55174
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55174&action=edit
packet-rnsap-shrunk-slightly.c.i.xz
packet-rnsap-shrunk-slightly.c.i.xz is a slightly shrunk version of the
original.
It exhibits 10x slowdown and has a reasonable compilation completion time.
Might be useful to explore as is or bisect gcc:
$ gcc -O2 -c packet-rnsap-shrunk-slightly.c.i -o bug.o -fipa-pta
-Wno-deprecated-declarations -fno-ipa-pta >/dev/null 2>&1
real 0m0,657s
user 0m0,626s
sys 0m0,026s
$ gcc -O2 -c packet-rnsap-shrunk-slightly.c.i -o bug.o -fipa-pta
-Wno-deprecated-declarations -fipa-pta >/dev/null 2>&1
real 0m6,120s
user 0m6,065s
sys 0m0,045s
-ftime-report says 'ipa points-to' takes 88%.
-fdump-ipa-all-details creates 2.0G bug.i.092i.pta2 file (the rest of files are
unred 5M).
I suspect it's a pathology in solving a huge `proto_reg_handoff_rnsap()` graph.
Some variables have up to 5000 PT entries.
next prev parent reply other threads:[~2023-05-26 18:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 9:26 [Bug ipa/109983] New: " sjames at gcc dot gnu.org
2023-05-26 9:28 ` [Bug ipa/109983] " sjames at gcc dot gnu.org
2023-05-26 9:36 ` sjames at gcc dot gnu.org
2023-05-26 10:38 ` slyfox at gcc dot gnu.org
2023-05-26 10:48 ` sjames at gcc dot gnu.org
2023-05-26 11:04 ` slyfox at gcc dot gnu.org
2023-05-26 18:17 ` slyfox at gcc dot gnu.org [this message]
2023-05-26 20:03 ` slyfox at gcc dot gnu.org
2023-05-26 20:09 ` pinskia at gcc dot gnu.org
2023-05-30 7:25 ` rguenth at gcc dot gnu.org
2023-05-30 8:39 ` rguenth at gcc dot gnu.org
2023-05-30 9:08 ` rguenth at gcc dot gnu.org
2023-05-31 10:37 ` rguenth at gcc dot gnu.org
2023-05-31 10:49 ` rguenth at gcc dot gnu.org
2023-05-31 11:27 ` cvs-commit at gcc dot gnu.org
2023-05-31 11:27 ` rguenth at gcc dot gnu.org
2023-05-31 19:27 ` [Bug ipa/109983] [12/13 " sjames at gcc dot gnu.org
2023-06-06 8:42 ` rguenth at gcc dot gnu.org
2023-06-23 10:29 ` cvs-commit at gcc dot gnu.org
2023-11-27 11:34 ` [Bug ipa/109983] [12 " cvs-commit at gcc dot gnu.org
2023-11-27 11:38 ` 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-109983-4-SZbDzEMpbg@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).