public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105461] [12 Regression] ICE: Segmentation fault (in verify_use) since r12-4608-gb4702276615ff8d4
Date: Fri, 06 May 2022 09:28:10 +0000 [thread overview]
Message-ID: <bug-105461-4-DahWdhAb4x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105461-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105461
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:1b13a6e0dc2f61fc26ebfd33ee8549da45286f34
commit r12-8344-g1b13a6e0dc2f61fc26ebfd33ee8549da45286f34
Author: Richard Biener <rguenther@suse.de>
Date: Tue May 3 10:36:30 2022 +0200
middle-end/105461 - opts processing of -fvar-tracking
The flag_var_tracking reset in finish_options doesn't match the
condition in process_options, in particular we fail to reset it
when the option was specified on the command line. The following
fixes this and also alters the debug info level guard to match
the one in process_options.
2022-05-03 Richard Biener <rguenther@suse.de>
PR middle-end/105461
* opts.cc (finish_options): Match the condition to
disable flag_var_tracking to that of process_options.
* gcc.dg/pr105461.c: New testcase.
(cherry picked from commit 6b4cc784806ac8676a08ecbbeadbd1bfa56073bb)
next prev parent reply other threads:[~2022-05-06 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 7:12 [Bug tree-optimization/105461] New: ICE: Segmentation fault (in verify_use) asolokha at gmx dot com
2022-05-03 7:50 ` [Bug tree-optimization/105461] " rguenth at gcc dot gnu.org
2022-05-03 8:14 ` [Bug tree-optimization/105461] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-05-03 8:18 ` [Bug tree-optimization/105461] [12/13 Regression] ICE: Segmentation fault (in verify_use) since r12-4608-gb4702276615ff8d4 marxin at gcc dot gnu.org
2022-05-03 8:23 ` rguenth at gcc dot gnu.org
2022-05-03 10:33 ` cvs-commit at gcc dot gnu.org
2022-05-06 8:33 ` [Bug tree-optimization/105461] [12 " jakub at gcc dot gnu.org
2022-05-06 9:28 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-06 9:29 ` 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-105461-4-DahWdhAb4x@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).