public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/109983] New: [12/13/14 regression] Wireshark compilation hangs with -O2 -fipa-pta
Date: Fri, 26 May 2023 09:26:11 +0000 [thread overview]
Message-ID: <bug-109983-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109983
Bug ID: 109983
Summary: [12/13/14 regression] Wireshark compilation hangs with
-O2 -fipa-pta
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: sjames at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Created attachment 55165
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55165&action=edit
packet-rnsap.c.i.xz
Originally reported downstream in Gentoo at https://bugs.gentoo.org/907182.
Building Wireshark with -fipa-pta ends up hanging when compiling
packet-rnsap.c.
It's enough to just try to build the reproducer with -O2 -fipa-pta for me
(actually, -O1 hangs too):
```
$ gcc-12 -O2 -fipa-pta -c packet-rnsap.c.i
[... hangs ...]
```
gcc 11.3.1 20230518 doesn't hang, while 12.3.1 20230519 / 13.1.1 20230520 /
14.0.0 20230521 do.
next reply other threads:[~2023-05-26 9:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 9:26 sjames at gcc dot gnu.org [this message]
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
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@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).