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 tree-optimization/113144] [14 regression] ICE when building dpkg-1.21.15 in verify_dominators (error: dominator of 9 should be 48, not 12)
Date: Thu, 28 Dec 2023 11:28:13 +0000 [thread overview]
Message-ID: <bug-113144-4-QalglsaYBi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113144-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113144
David Binderman <dcb314 at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dcb314 at hotmail dot com
--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
I see this one also, while building libmpg.
foundBugs $ ../results/bin/gcc -c -w -O3 bug993.c
foundBugs $ ../results/bin/gcc -c -w -O3 -march=znver3 bug993.c
src/libmpg123/format.c: In function ‘enc_chan_fit’:
src/libmpg123/format.c:188:12: error: dominator of 70 should be 206, not 3
src/libmpg123/format.c:188:12: error: dominator of 71 should be 206, not 3
during GIMPLE pass: vect
src/libmpg123/format.c:188:12: internal compiler error: in verify_dominators,
at dominance.cc:1194
next prev parent reply other threads:[~2023-12-28 11:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 6:55 [Bug tree-optimization/113144] New: " sjames at gcc dot gnu.org
2023-12-26 6:55 ` [Bug tree-optimization/113144] " sjames at gcc dot gnu.org
2023-12-26 7:01 ` sjames at gcc dot gnu.org
2023-12-26 14:14 ` tnfchris at gcc dot gnu.org
2023-12-26 14:28 ` tnfchris at gcc dot gnu.org
2023-12-27 11:54 ` tnfchris at gcc dot gnu.org
2023-12-27 11:55 ` tnfchris at gcc dot gnu.org
2023-12-28 11:28 ` dcb314 at hotmail dot com [this message]
2023-12-29 21:07 ` tnfchris at gcc dot gnu.org
2024-01-05 13:18 ` tnfchris at gcc dot gnu.org
2024-01-08 19:37 ` zsojka at seznam dot cz
2024-01-08 19:55 ` pinskia at gcc dot gnu.org
2024-01-09 3:49 ` tnfchris at gcc dot gnu.org
2024-01-09 17:14 ` jamborm at gcc dot gnu.org
2024-01-09 19:08 ` tnfchris at gcc dot gnu.org
2024-01-09 22:21 ` tnfchris at gcc dot gnu.org
2024-01-10 12:54 ` cvs-commit at gcc dot gnu.org
2024-01-10 12:56 ` tnfchris 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-113144-4-QalglsaYBi@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).