public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64498] [5 Regression] Cannot build Firefox with LTO: ICE in substitute_and_fold_dom_walker::before_dom_children
Date: Mon, 12 Jan 2015 09:02:00 -0000 [thread overview]
Message-ID: <bug-64498-4-tkddkAsXUT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64498-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64498
--- Comment #2 from Jan Hubicka <hubicka at ucw dot cz> ---
> Problem is hidden in flag_var_tracking_assignments, which is set to false.
> Thus, MAY_HAVE_DEBUG_INSNS is set to false. Unfortunately, Firefox contains
> couple of third party libraries that have -g as a default option. So that DCE
> after a statements removal does not remove debug statements that use result of
> a statement and verifier fails.
flag_var_tracking_assignments is marked as Optimization in common.opt while
rest
of debug machinery is not Optimization. This means that we try to preserve
assignments
in functions that was compiled with -g at compile time, but then we never
consume
it....
Shall we drop flag_var_tracking_assignments to 0 and remove the debug
statements after streaming in in these cases? Also inliner probably needs to
remove the statements when it inlines from function with
flag_var_tracking_assignments to one with !flag_var_tracking_assignments
Honza
next prev parent reply other threads:[~2015-01-12 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 10:46 [Bug middle-end/64498] New: " marxin at gcc dot gnu.org
2015-01-09 11:20 ` [Bug middle-end/64498] " rguenth at gcc dot gnu.org
2015-01-12 8:56 ` marxin at gcc dot gnu.org
2015-01-12 9:02 ` hubicka at ucw dot cz [this message]
2015-01-13 12:34 ` rguenth at gcc dot gnu.org
2015-01-14 15:27 ` rguenth at gcc dot gnu.org
2015-01-14 16:17 ` marxin 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-64498-4-tkddkAsXUT@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).