public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114855] ICE: Segfault
Date: Sat, 22 Jun 2024 13:08:26 +0000 [thread overview]
Message-ID: <bug-114855-4-rWzjcF3vmK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114855-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note looking at -O1 is the most important thing, as we tell people to use -O1
for autogenerated code. There I suppose comment#4 still applies and likely
this is ranger as well. Maybe DOMs ranger use can be tuned down at -O1
(when -ftree-vrp is off).
next prev parent reply other threads:[~2024-06-22 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 20:00 [Bug c/114855] New: " jeremy.rutman at gmail dot com
2024-04-25 20:09 ` [Bug middle-end/114855] " pinskia at gcc dot gnu.org
2024-04-25 20:13 ` pinskia at gcc dot gnu.org
2024-04-26 6:00 ` jeremy.rutman at gmail dot com
2024-04-26 14:25 ` rguenth at gcc dot gnu.org
2024-04-26 19:50 ` jeremy.rutman at gmail dot com
2024-04-30 9:13 ` rguenth at gcc dot gnu.org
2024-05-03 21:46 ` amacleod at redhat dot com
2024-05-09 15:57 ` amacleod at redhat dot com
2024-06-22 13:08 ` rguenth at gcc dot gnu.org [this message]
2024-06-24 13:04 ` rguenth at gcc dot gnu.org
2024-06-24 13:14 ` rguenth at gcc dot gnu.org
2024-06-24 14:47 ` rguenth at gcc dot gnu.org
2024-06-25 9:23 ` 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-114855-4-rWzjcF3vmK@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).