public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/55257] New: [4.8 Regression]: g++.dg/debug/dwarf2/non-virtual-thunk.C scan-assembler thunk.C:30
Date: Sat, 10 Nov 2012 01:52:00 -0000	[thread overview]
Message-ID: <bug-55257-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55257
           Summary: [4.8 Regression]:
                    g++.dg/debug/dwarf2/non-virtual-thunk.C scan-assembler
                    thunk.C:30
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: wrong-debug
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hp@gcc.gnu.org
                CC: jakub@gcc.gnu.org
              Host: x86_64-unknown-linux-gnu
            Target: cris-axis-elf


Created attachment 28649
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28649
non-virtual-thunk.s

This test previously passed, now it fails.
A patch in the revision range (last_known_working:first_known_failing)
193333:193342 exposed or caused this regression.  Since then it fails as
follows:

Running /tmp/hpautotest-gcc0/gcc/gcc/testsuite/g++.dg/debug/dwarf2/dwarf2.exp
...
FAIL: g++.dg/debug/dwarf2/non-virtual-thunk.C -std=gnu++98  scan-assembler
thunk.C:30
FAIL: g++.dg/debug/dwarf2/non-virtual-thunk.C -std=gnu++11  scan-assembler
thunk.C:30

No extra clue in g++.log.
Executing on host:
/tmp/hpautotest-gcc0/cris-elf/gccobj/gcc/testsuite/g++/../../g++
-B/tmp/hpautotest-gcc0/cris-elf/gccobj/gcc/testsuite/g++/../../
/tmp/hpautotest-gcc0/gcc/gcc/testsuite/g++.dg/debug/dwarf2/non-virtual-thunk.C 
-fno-diagnostics-show-caret  -nostdinc++
-I/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/libstdc++-v3/include/cris-elf
-I/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/libstdc++-v3/include
-I/tmp/hpautotest-gcc0/gcc/libstdc++-v3/libsupc++
-I/tmp/hpautotest-gcc0/gcc/libstdc++-v3/include/backward
-I/tmp/hpautotest-gcc0/gcc/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++98 -g2 -dA -ffat-lto-objects  -S   -isystem
/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/./newlib/targ-include -isystem
/tmp/hpautotest-gcc0/gcc/newlib/libc/include  -o non-virtual-thunk.s   
(timeout = 300)
PASS: g++.dg/debug/dwarf2/non-virtual-thunk.C -std=gnu++98 (test for excess
errors)
FAIL: g++.dg/debug/dwarf2/non-virtual-thunk.C -std=gnu++98  scan-assembler
thunk.C:30

(same for -std=gnu++11)

There's no "thunk.C:30" in the assembly file, just lots of:
"<TAB>;#
/tmp/hpautotest-gcc0/gcc/gcc/testsuite/g++.dg/debug/dwarf2/non-virtual-thunk.C:33"

See the attached non-virtual-thunk.s.

Author of suspect patch in revision range CC:ed.


             reply	other threads:[~2012-11-10  1:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10  1:52 hp at gcc dot gnu.org [this message]
2012-11-12  7:51 ` [Bug debug/55257] " jakub at gcc dot gnu.org
2012-11-12 17:08 ` hp at gcc dot gnu.org
2012-11-12 17:15 ` jakub at gcc dot gnu.org
2012-11-12 17:22 ` hp at gcc dot gnu.org
2012-11-13  6:14 ` [Bug target/55257] " hp at gcc dot gnu.org
2012-11-13  6:16 ` hp at gcc dot gnu.org
2012-11-13  6:39 ` hp 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-55257-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).