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/56307] FAIL: gcc.dg/tree-ssa/pr55579.c scan-tree-dump esra "Created a debug-only replacement for s"
Date: Wed, 13 Mar 2013 14:33:00 -0000	[thread overview]
Message-ID: <bug-56307-4-050mUMxQam@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56307-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-03-13 14:33:07 UTC ---
Ah yes, I forgot that all of -fvar-tracking is disabled for non-dwarf debug.
Yeah, passing -fvar-tracking -fvar-tracking-assignments in dg-options is
desirable for that test.  The test isn't -O3, so not even on ia64 sel-sched
will be on by default.


  parent reply	other threads:[~2013-03-13 14:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 14:37 [Bug debug/56307] New: " danglin at gcc dot gnu.org
2013-02-14 10:35 ` [Bug debug/56307] " rguenth at gcc dot gnu.org
2013-02-18 10:55 ` jamborm at gcc dot gnu.org
2013-03-09 22:49 ` danglin at gcc dot gnu.org
2013-03-11  1:10 ` danglin at gcc dot gnu.org
2013-03-12  1:06 ` danglin at gcc dot gnu.org
2013-03-12  8:32 ` jamborm at gcc dot gnu.org
2013-03-12 14:52 ` danglin at gcc dot gnu.org
2013-03-12 14:53 ` danglin at gcc dot gnu.org
2013-03-12 17:48 ` jamborm at gcc dot gnu.org
2013-03-12 18:00 ` jakub at gcc dot gnu.org
2013-03-12 18:27 ` dave.anglin at bell dot net
2013-03-13  1:50 ` dave.anglin at bell dot net
2013-03-13  2:08 ` danglin at gcc dot gnu.org
2013-03-13 14:33 ` jakub at gcc dot gnu.org [this message]
2013-03-14 23:46 ` danglin at gcc dot gnu.org
2013-03-15  7:07 ` jakub at gcc dot gnu.org
2013-07-28 19:05 ` danglin 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-56307-4-050mUMxQam@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).