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/54230] New: g++.dg/debug/dwarf2/pubnames-2.C failures on darwin12
Date: Sat, 11 Aug 2012 19:07:00 -0000	[thread overview]
Message-ID: <bug-54230-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 54230
           Summary: g++.dg/debug/dwarf2/pubnames-2.C failures on darwin12
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: howarth@nitro.med.uc.edu


Created attachment 27991
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27991
assembly from failing m32 test of g++.dg/debug/dwarf2/pubnames-2.C on darwin12

The new g++.dg/debug/dwarf2/pubnames-2.C testcase produces the failures...

Native configuration is x86_64-apple-darwin12.0.0

        === g++ tests ===

Schedule of variations:
    unix/-m32
    unix/-m64

Running target unix/-m32
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /Users/howarth/gcc-4.8-20120810/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running
/Users/howarth/gcc-4.8-20120810/gcc/testsuite/g++.dg/debug/dwarf2/dwarf2.exp
...
FAIL: g++.dg/debug/dwarf2/pubnames-2.C scan-assembler .section\t.debug_pubnames
FAIL: g++.dg/debug/dwarf2/pubnames-2.C scan-assembler
"_GLOBAL__sub_I__ZN3one3c1vE\\\\0"+[ \t]+[#;]+[ \t]+external name
FAIL: g++.dg/debug/dwarf2/pubnames-2.C scan-assembler .section\t.debug_pubtypes

        === g++ Summary for unix/-m32 ===

# of expected passes        1250
# of unexpected failures    3
# of unsupported tests        6
Running target unix/-m64
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /Users/howarth/gcc-4.8-20120810/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running
/Users/howarth/gcc-4.8-20120810/gcc/testsuite/g++.dg/debug/dwarf2/dwarf2.exp
...
FAIL: g++.dg/debug/dwarf2/pubnames-2.C scan-assembler .section\t.debug_pubnames
FAIL: g++.dg/debug/dwarf2/pubnames-2.C scan-assembler
"_GLOBAL__sub_I__ZN3one3c1vE\\\\0"+[ \t]+[#;]+[ \t]+external name
FAIL: g++.dg/debug/dwarf2/pubnames-2.C scan-assembler .section\t.debug_pubtypes

        === g++ Summary for unix/-m64 ===

# of expected passes        1250
# of unexpected failures    3
# of unsupported tests        6

        === g++ Summary ===

# of expected passes        2500
# of unexpected failures    6
# of unsupported tests        12
/Users/howarth/work/gcc/testsuite/g++/../../g++  version 4.8.0 20120709
(experimental) (GCC) 

at both r189392 when the testcase was introduced as well as in current gcc
trunk.


             reply	other threads:[~2012-08-11 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-11 19:07 howarth at nitro dot med.uc.edu [this message]
2012-08-20 12:37 ` [Bug debug/54230] " dominiq at lps dot ens.fr
2012-12-09 14:36 ` howarth at nitro dot med.uc.edu

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-54230-4@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).