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/54693] VTA guality issues with loops
Date: Mon, 01 Oct 2012 15:26:00 -0000	[thread overview]
Message-ID: <bug-54693-4-TCVnKnvSUQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54693-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-10-01 15:26:10 UTC ---
In VRP it is jump threading that performs the first CFG transformation, and the
second one happens as two merge_block opportunities during cleanup_tree_cfg.
Doing the new DEBUG stmt insertion upon merge_blocks would be weird, perhaps
some pass should just in addition to what it does now try to detect at least
the simple cases, where at the end of more than one predecessor block are live
debug stmts for some decl, and they use invariants or SSA_NAMEs that appear
together in some PHI - then adding a DEBUG stmt at the start of the bb with a
PHI might improve debug info quality, something var-tracking won't be able to
figure out due to the conditional.


  reply	other threads:[~2012-10-01 15:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 13:41 [Bug debug/54693] New: " jakub at gcc dot gnu.org
2012-10-01 15:26 ` jakub at gcc dot gnu.org [this message]
2012-10-04  6:10 ` [Bug debug/54693] " jakub at gcc dot gnu.org
2012-10-14 21:19 ` aoliva at gcc dot gnu.org
2012-10-19 12:34 ` jakub at gcc dot gnu.org
2012-10-19 13:49 ` jakub at gcc dot gnu.org
2012-10-26  7:17 ` aoliva at gcc dot gnu.org
2012-10-29 19:26 ` aoliva at gcc dot gnu.org
2012-10-29 19:27 ` aoliva at gcc dot gnu.org
2012-10-29 19:28 ` aoliva at gcc dot gnu.org
2012-10-29 19:37 ` aoliva at gcc dot gnu.org
2012-10-29 19:37 ` aoliva at gcc dot gnu.org
2012-10-30 23:48 ` aoliva at gcc dot gnu.org
2012-11-04 18:44 ` aoliva at gcc dot gnu.org
2012-11-04 18:44 ` aoliva at gcc dot gnu.org
2012-11-04 22:09 ` aoliva at gcc dot gnu.org
2012-11-06  9:46 ` jakub at gcc dot gnu.org
2012-11-06 17:59 ` aoliva at gcc dot gnu.org
2012-11-07  7:50 ` jakub at gcc dot gnu.org
2012-11-17 10:01 ` andreast at gcc dot gnu.org
2012-11-17 12:36 ` andreast at gcc dot gnu.org
2012-11-18  1:56 ` aoliva 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-54693-4-TCVnKnvSUQ@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).