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/110874] [14 Regression] ice with -O2 with recent gcc
Date: Wed, 02 Aug 2023 20:17:08 +0000 [thread overview]
Message-ID: <bug-110874-4-KPjqFqn7b0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110874-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110874
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to David Binderman from comment #6)
> (In reply to Andrew Pinski from comment #4)
> > There is a stack overflow while executing the FRE pass.
>
> I can confirm over 100,000 stack frames.
>
> Which -f flag causes the FRE pass to be executed ?
> I assume it is in -O2, but not in -O1.
Fre is enabled at -O1 but the IR changes before fre. I have not looked into
what changes to the IR on why there is a difference between -O1 and -O2 yet.
next prev parent reply other threads:[~2023-08-02 20:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 13:46 [Bug c/110874] New: " dcb314 at hotmail dot com
2023-08-02 15:23 ` [Bug c/110874] " dcb314 at hotmail dot com
2023-08-02 15:58 ` [Bug middle-end/110874] [14 Regression] " pinskia at gcc dot gnu.org
2023-08-02 16:12 ` pinskia at gcc dot gnu.org
2023-08-02 16:59 ` pinskia at gcc dot gnu.org
2023-08-02 20:11 ` dcb314 at hotmail dot com
2023-08-02 20:14 ` dcb314 at hotmail dot com
2023-08-02 20:17 ` pinskia at gcc dot gnu.org [this message]
2023-08-02 20:32 ` pinskia at gcc dot gnu.org
2023-08-02 21:01 ` pinskia at gcc dot gnu.org
2023-08-02 21:09 ` pinskia at gcc dot gnu.org
2023-08-03 2:44 ` pinskia at gcc dot gnu.org
2023-08-03 6:59 ` pinskia at gcc dot gnu.org
2023-08-03 7:18 ` pinskia at gcc dot gnu.org
2023-08-03 22:49 ` pinskia at gcc dot gnu.org
2023-08-04 7:27 ` cvs-commit at gcc dot gnu.org
2023-08-04 7:27 ` pinskia 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-110874-4-KPjqFqn7b0@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).