public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/53363] g++.dg/debug/dwarf2/thunk1.C FAILs
Date: Tue, 15 May 2012 19:15:00 -0000	[thread overview]
Message-ID: <bug-53363-4-6Nz8CvqSLS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53363-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Jason Merrill <jason at gcc dot gnu.org> 2012-05-15 19:09:37 UTC ---
Yes, the test should only run in 32-bit mode.

For me, on i686-unknown-linux-gnu the test passes.  What are the uses of LFB3
on Solaris for?


  reply	other threads:[~2012-05-15 19:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 15:51 [Bug debug/53363] New: " ro at gcc dot gnu.org
2012-05-15 19:15 ` jason at gcc dot gnu.org [this message]
2012-05-16 11:07 ` [Bug debug/53363] " ro at CeBiTec dot Uni-Bielefeld.DE
2012-05-16 11:07 ` ro at gcc dot gnu.org
2012-05-16 11:08 ` ro at gcc dot gnu.org
2013-02-05 10:24 ` ro at gcc dot gnu.org
2013-02-05 10:26 ` ro at gcc dot gnu.org
2013-02-06 18:27 ` jason at gcc dot gnu.org
2013-02-07  9:56 ` ro at gcc dot gnu.org
2013-02-07 10:07 ` ro at gcc dot gnu.org
2013-03-05 13:44 ` howarth at nitro dot med.uc.edu
2013-03-05 13:48 ` howarth at nitro dot med.uc.edu
2013-03-05 14:21 ` jason at gcc dot gnu.org
2013-03-05 15:02 ` howarth at nitro dot med.uc.edu
2013-03-05 15:12 ` dominiq at lps dot ens.fr
2013-03-05 15:41 ` jason at gcc dot gnu.org
2013-03-05 16:55 ` howarth at nitro dot med.uc.edu
2013-03-05 19:01 ` jason at gcc dot gnu.org
2013-03-05 22:20 ` howarth at nitro dot med.uc.edu
2013-03-06 15:34 ` jason at gcc dot gnu.org
2013-03-22 14:45 ` jakub at gcc dot gnu.org
2013-05-31 10:59 ` jakub at gcc dot gnu.org
2013-10-16  9:51 ` jakub at gcc dot gnu.org
2015-06-22 14:26 ` rguenth 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-53363-4-6Nz8CvqSLS@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).