public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/50317] [4.7 Regression] missing DW_OP_GNU_implicit_pointer
Date: Mon, 28 Nov 2011 14:22:00 -0000	[thread overview]
Message-ID: <bug-50317-4-iuzkkfzl4q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50317-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50317

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-11-28 14:10:40 UTC ---
Perhaps we could drop the var ={v} {CLOBBER} stmts when renaming the var into
SSA instead.

As for gcc47-pr50317-1.patch, the another walk isn't because of the CLOBBERs,
what it tries to solve is drop the ADDRESSABLE bit before CDDCE decides to
instead optimize all the stores away as unnecessary (the former does the right
thing for debug info, the latter does not).

The reason why the gcc/tree-ssa-dce.c change doesn't work is that currently we
rely on the var in debug stmts to be target_for_debug_bind (which among other
conditions means is_gimple_reg).  That patch emits debug stmts even for cases
where the var is not is_gimple_reg because of TREE_ADDRESSABLE.  As nothing
drops the TREE_ADDRESSABLE bit later on (on this testcase we could do it
somewhere, but not generally, consider e.g. where the first store into some
addressable var is necessary, but last store is not).  DCE at this point
doesn't know if it is removing all references of the addressable var from the
IL.
Passes that are upset about the !target_for_debug_bind var in debug stmts/debug
insns are expansion (it doesn't ICE, but doesn't create the implicit pointer
because the var whose address is taken is addressable) and var-tracking (for
which it leads to ICEs because VALUE is propagated through into the notes).


  parent reply	other threads:[~2011-11-28 14:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 10:57 [Bug debug/50317] New: " jan.kratochvil at redhat dot com
2011-09-07 14:13 ` [Bug debug/50317] " jakub at gcc dot gnu.org
2011-09-07 14:23 ` jakub at gcc dot gnu.org
2011-10-27 10:18 ` rguenth at gcc dot gnu.org
2011-10-27 13:58 ` jan.kratochvil at redhat dot com
2011-11-28 13:25 ` jakub at gcc dot gnu.org
2011-11-28 13:43 ` jakub at gcc dot gnu.org
2011-11-28 14:18 ` matz at gcc dot gnu.org
2011-11-28 14:22 ` jakub at gcc dot gnu.org [this message]
2011-11-28 14:48 ` jakub at gcc dot gnu.org
2011-11-28 15:18 ` matz at gcc dot gnu.org
2011-11-28 15:41 ` jakub at gcc dot gnu.org
2011-11-28 21:06 ` jakub at gcc dot gnu.org
2011-12-01 19:13 ` jakub at gcc dot gnu.org
2011-12-01 19:18 ` jakub at gcc dot gnu.org
2011-12-03 16:40 ` jakub 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-50317-4-iuzkkfzl4q@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).