public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/54970] Missing DW_OP_GNU_implicit_pointer in debuginfo
Date: Tue, 12 Mar 2013 18:55:00 -0000	[thread overview]
Message-ID: <bug-54970-4-2G1bgfcTA5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54970-4@http.gcc.gnu.org/bugzilla/>


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

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steven at gcc dot gnu.org

--- Comment #8 from Steven Bosscher <steven at gcc dot gnu.org> 2013-03-12 18:55:19 UTC ---
(In reply to comment #7)
> The stores are of course optimized away, everywhere, that is the point
> of the testcase.

I am talking about the debug_stmts for the stores, sorry if that was not
clear.  On x86_64 the test case passes, but on powerpc64 esra does something
it doesn't do on x86_64 and it makes the test case fail.  Is there a known
bug for that already, also?

This is 176 FAILs on powerpc64.  If it's "supposed to not work" there, then
the test case should be XFAIL'ed there.


      parent reply	other threads:[~2013-03-12 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  8:45 [Bug debug/54970] New: " jakub at gcc dot gnu.org
2012-10-18  8:46 ` [Bug debug/54970] " jakub at gcc dot gnu.org
2012-10-18  8:55 ` jakub at gcc dot gnu.org
2012-10-18  9:27 ` jakub at gcc dot gnu.org
2012-10-26 19:20 ` jakub at gcc dot gnu.org
2012-11-05 14:37 ` jakub at gcc dot gnu.org
2012-12-04 13:17 ` jakub at gcc dot gnu.org
2013-03-12 17:09 ` steven at gcc dot gnu.org
2013-03-12 17:51 ` jakub at gcc dot gnu.org
2013-03-12 18:55 ` steven at gcc dot gnu.org [this message]

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-54970-4-2G1bgfcTA5@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).