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/64415] [5 Regression] ICE: verify_ssa failed / segmentation fault with LTO
Date: Tue, 13 Jan 2015 13:06:00 -0000 [thread overview]
Message-ID: <bug-64415-4-q1VwGGlKO4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64415-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64415
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Same issue as noted elsewhere - -fvar-tracking-assignments shouldn't be in
TARGET_OPTIMIZATION_NODE. I am testing
Index: gcc/common.opt
===================================================================
--- gcc/common.opt (revision 219520)
+++ gcc/common.opt (working copy)
@@ -2397,13 +2397,13 @@ Perform variable tracking
; annotations. When flag_var_tracking_assignments ==
; AUTODETECT_VALUE it will be set according to flag_var_tracking.
fvar-tracking-assignments
-Common Report Var(flag_var_tracking_assignments) Init(2) Optimization
+Common Report Var(flag_var_tracking_assignments) Init(2)
Perform variable tracking by annotating assignments
; Nonzero if we should toggle flag_var_tracking_assignments after
; processing options and computing its default. */
fvar-tracking-assignments-toggle
-Common Report Var(flag_var_tracking_assignments_toggle) Optimization
+Common Report Var(flag_var_tracking_assignments_toggle)
Toggle -fvar-tracking-assignments
; Positive if we should track uninitialized variables, negative if
next prev parent reply other threads:[~2015-01-13 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 22:34 [Bug middle-end/64415] New: " d.g.gorbachev at gmail dot com
2015-01-05 9:41 ` [Bug middle-end/64415] " mpolacek at gcc dot gnu.org
2015-01-05 16:58 ` hjl.tools at gmail dot com
2015-01-13 11:00 ` rguenth at gcc dot gnu.org
2015-01-13 13:06 ` rguenth at gcc dot gnu.org [this message]
2015-01-14 11:06 ` rguenth at gcc dot gnu.org
2015-01-14 11:06 ` rguenth at gcc dot gnu.org
2015-01-14 15:27 ` rguenth at gcc dot gnu.org
2015-01-15 11:43 ` rguenth at gcc dot gnu.org
2015-01-15 12:19 ` 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-64415-4-q1VwGGlKO4@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).