public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114081] [14 regression] ICE in verify_dominators when building php-8.3.3 (error: dominator of 16 should be 111, not 3)
Date: Fri, 23 Feb 2024 18:21:04 +0000 [thread overview]
Message-ID: <bug-114081-4-OGRBjfG8LY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114081-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114081
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Sam James from comment #1)
> I can reproduce with: gcc -c ./ext/filter/filter.i -march=znver2
> -fno-vect-cost-model -O3.
`-O3 -fno-vect-cost-model -mavx2` is enough with my reduced testcase.
next prev parent reply other threads:[~2024-02-23 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:14 [Bug middle-end/114081] New: " sjames at gcc dot gnu.org
2024-02-23 16:15 ` [Bug middle-end/114081] " sjames at gcc dot gnu.org
2024-02-23 17:48 ` pinskia at gcc dot gnu.org
2024-02-23 18:18 ` pinskia at gcc dot gnu.org
2024-02-23 18:18 ` pinskia at gcc dot gnu.org
2024-02-23 18:21 ` pinskia at gcc dot gnu.org [this message]
2024-02-23 18:28 ` [Bug middle-end/114081] [14 regression] ICE in verify_dominators when building php-8.3.3 (error: dominator of 16 should be 111, not 3) since r14-6822 jakub at gcc dot gnu.org
2024-02-23 18:28 ` jakub at gcc dot gnu.org
2024-02-23 19:04 ` tnfchris at gcc dot gnu.org
2024-02-25 15:43 ` sjames at gcc dot gnu.org
2024-02-27 8:12 ` cvs-commit at gcc dot gnu.org
2024-02-27 8:12 ` 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-114081-4-OGRBjfG8LY@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).