public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/53363] g++.dg/debug/dwarf2/thunk1.C FAILs
Date: Tue, 05 Mar 2013 16:55:00 -0000 [thread overview]
Message-ID: <bug-53363-4-f74g87hAMd@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 #15 from Jack Howarth <howarth at nitro dot med.uc.edu> 2013-03-05 16:55:07 UTC ---
(In reply to comment #14)
> (In reply to comment #13)
> > What is supposed to be tested? Should the whole test skipped on darwin or only
> > the dg-final?
>
> The whole test; the test is verifying that the x86 PIC thunk doesn't have debug
> info, but Darwin doesn't emit that thunk.
Any idea how to disable this on darwin? While...
// { dg-do compile { target { { i?86-*-* || x86_64-*-* } && { ! *-*-darwin* } }
} }
parses in dejagnu, the required...
// { dg-do compile { target { { i?86-*-* || x86_64-*-* } && { ! *-*-darwin* }
&& ia32 } } }
doesn't...
ERROR: g++.dg/debug/dwarf2/thunk1.C -std=gnu++98: syntax error in target
selector "target i?86-*-* || x86_64-*-* && ! *-*-darwin* && ia32" for "
dg-do 2 compile { target { { i?86-*-* || x86_64-*-* } && { ! *-*-darwin* } && {
ia32 } } } "
next prev parent reply other threads:[~2013-03-05 16:55 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 ` [Bug debug/53363] " jason at gcc dot gnu.org
2012-05-16 11:07 ` ro at gcc dot gnu.org
2012-05-16 11:07 ` ro at CeBiTec dot Uni-Bielefeld.DE
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 [this message]
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-f74g87hAMd@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).