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: Wed, 14 Jan 2015 11:06:00 -0000 [thread overview]
Message-ID: <bug-64415-4-CpQQ2ZLowL@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
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Wed Jan 14 11:06:18 2015
New Revision: 219588
URL: https://gcc.gnu.org/viewcvs?rev=219588&root=gcc&view=rev
Log:
2015-01-14 Richard Biener <rguenther@suse.de>
PR lto/64415
* tree-inline.c (insert_debug_decl_map): Check destination
function MAY_HAVE_DEBUG_STMTS.
(insert_init_debug_bind): Likewise.
(insert_init_stmt): Remove redundant check.
(remap_gimple_stmt): Drop debug stmts if the destination
function has var-tracking assignments disabled.
* gcc.dg/lto/pr64415_0.c: New testcase.
* gcc.dg/lto/pr64415_1.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/lto/pr64415_0.c
trunk/gcc/testsuite/gcc.dg/lto/pr64415_1.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-inline.c
next prev parent reply other threads:[~2015-01-14 11: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
2015-01-14 11:06 ` rguenth at gcc dot gnu.org
2015-01-14 11:06 ` rguenth at gcc dot gnu.org [this message]
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-CpQQ2ZLowL@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).