public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldot at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/52665] New: scan-assembler output produces wrong FAIL due to matching .ident
Date: Thu, 22 Mar 2012 12:02:00 -0000	[thread overview]
Message-ID: <bug-52665-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52665
           Summary: scan-assembler output produces wrong FAIL due to
                    matching .ident
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: aldot@gcc.gnu.org


I see this regression:
FAIL: gcc.target/i386/pr28946.c scan-assembler-not test

The culprit is the testsuite errnoeously matching my local branch name in the
assembler output's .ident.

$ grep scan ../../src/gcc-4.8/gcc/testsuite/gcc.target/i386/pr28946.c
/* { dg-final { scan-assembler-not "test" } } */

$ ./gcc/xgcc -B/scratch/obj.x86_64/gcc-4.8/gcc/
../../src/gcc-4.8/gcc/testsuite/gcc.target/i386/pr28946.c   -Os
-ffat-lto-objects -S  -o - | grep test
    .ident    "GCC: (GNU) 4.8.0 20120320 (experimental) [fixups-testsuite
revision 1dc2c94:40d1377:d28ff051e43bdf8f8aab692fbf6932a7211ca49d]"

Perhaps output for scan-assembler should be built with -fno-ident ?


             reply	other threads:[~2012-03-22 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 12:02 aldot at gcc dot gnu.org [this message]
2012-03-22 12:11 ` [Bug testsuite/52665] " aldot at gcc dot gnu.org
2012-03-27  7:04 ` aldot at gcc dot gnu.org
2012-03-27 18:03 ` mrs at gcc dot gnu.org
2012-03-27 18:09 ` mrs 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-52665-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).