public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113089] [14 Regression][aarch64] ICE in process_uses_of_deleted_def, at rtl-ssa/changes.cc:252 since r14-6605-gc0911c6b357ba9
Date: Wed, 20 Dec 2023 11:05:20 +0000 [thread overview]
Message-ID: <bug-113089-4-Z9VXpYZI84@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113089-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113089
--- Comment #9 from Alex Coplan <acoplan at gcc dot gnu.org> ---
(In reply to Manolis Tsamis from comment #8)
> (In reply to Alex Coplan from comment #7)
> > (In reply to Manolis Tsamis from comment #6)
> > > (In reply to Alex Coplan from comment #5)
> > > > Also ICEs without -fno-strict-aliasing FWIW, so just -g -O2 -funroll-loops
> > > > seems to be enough.
> > >
> > > On my local build it doesn't reproduce without -fno-strict-aliasing; I just
> > > double-checked (GCC master @ 4e0a467302fea56d63b7a6d17f99c0f388960dc7).
> >
> > Hmm, that is odd, I definitely don't need that option even when built from
> > the same commit. How are you configuring GCC? I suppose it doesn't matter
> > since I can reproduce the problem as long as the fix works with/without
> > -fno-strict-aliasing.
>
> Odd indeed, but probably something with my configure flags as you mentioned.
> Here's what I use:
>
> --enable-shared \
> --enable-threads=posix \
> --enable-checking=release \
> --with-system-zlib \
> --enable-__cxa_atexit \
> --disable-libunwind-exceptions \
> --enable-linker-build-id \
> --enable-libstdcxx-backtrace \
> --enable-plugin \
> --enable-initfini-array \
> --enable-gnu-indirect-function \
> --with-isl \
> --enable-lto \
> --with-cpu=neoverse-n1 \
> --disable-multilib \
> --disable-bootstrap
>
> (I think the most uncommon one here is --with-cpu=neoverse-n1 ?)
Ah, that explains it. I have a much more vanilla config, and indeed with
-mcpu=neoverse-n1 then it needs -fno-strict-aliasing to reproduce.
next prev parent reply other threads:[~2023-12-20 11:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 3:12 [Bug target/113089] New: " hliu at amperecomputing dot com
2023-12-20 3:14 ` [Bug target/113089] " pinskia at gcc dot gnu.org
2023-12-20 8:02 ` rguenth at gcc dot gnu.org
2023-12-20 10:21 ` manolis.tsamis at vrull dot eu
2023-12-20 10:22 ` manolis.tsamis at vrull dot eu
2023-12-20 10:30 ` acoplan at gcc dot gnu.org
2023-12-20 10:44 ` acoplan at gcc dot gnu.org
2023-12-20 10:48 ` manolis.tsamis at vrull dot eu
2023-12-20 10:59 ` acoplan at gcc dot gnu.org
2023-12-20 11:03 ` manolis.tsamis at vrull dot eu
2023-12-20 11:05 ` acoplan at gcc dot gnu.org [this message]
2023-12-20 12:08 ` acoplan at gcc dot gnu.org
2024-01-08 12:51 ` jakub at gcc dot gnu.org
2024-01-18 15:08 ` acoplan at gcc dot gnu.org
2024-01-19 9:18 ` acoplan at gcc dot gnu.org
2024-01-23 16:50 ` cvs-commit at gcc dot gnu.org
2024-01-23 16:51 ` cvs-commit at gcc dot gnu.org
2024-01-23 16:51 ` cvs-commit at gcc dot gnu.org
2024-01-23 16:55 ` acoplan 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-113089-4-Z9VXpYZI84@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).