public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100412] New: [11/12 regression] PASS & FAIL for same test aarch64-qemu: gcc.dg/Wvla-parameter-[23].c pr?????
Date: Tue, 04 May 2021 10:50:11 +0000	[thread overview]
Message-ID: <bug-100412-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100412

            Bug ID: 100412
           Summary: [11/12 regression] PASS & FAIL for same test
                    aarch64-qemu: gcc.dg/Wvla-parameter-[23].c pr?????
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rearnsha at gcc dot gnu.org
  Target Milestone: ---

contrig/test_summary on Arm and AArch64 shows both PASS and FAIL with the same
summary line.  

Tests that now fail, but worked before (6 tests):

aarch64-qemu: gcc.dg/Wvla-parameter-2.c pr????? (test for warnings, line 40)
aarch64-qemu: gcc.dg/Wvla-parameter-2.c pr????? (test for warnings, line 42)
aarch64-qemu: gcc.dg/Wvla-parameter-2.c pr????? (test for warnings, line 44)
aarch64-qemu: gcc.dg/Wvla-parameter-2.c pr????? (test for warnings, line 46)
aarch64-qemu: gcc.dg/Wvla-parameter-3.c pr????? (test for warnings, line 35)
aarch64-qemu: gcc.dg/Wvla-parameter-3.c pr????? (test for warnings, line 39)

Tests that now work, but didn't before (6 tests):

aarch64-qemu: gcc.dg/Wvla-parameter-2.c pr????? (test for warnings, line 40)
aarch64-qemu: gcc.dg/Wvla-parameter-2.c pr????? (test for warnings, line 42)
aarch64-qemu: gcc.dg/Wvla-parameter-2.c pr????? (test for warnings, line 44)
aarch64-qemu: gcc.dg/Wvla-parameter-2.c pr????? (test for warnings, line 46)
aarch64-qemu: gcc.dg/Wvla-parameter-3.c pr????? (test for warnings, line 35)
aarch64-qemu: gcc.dg/Wvla-parameter-3.c pr????? (test for warnings, line 39)

It looks like these tests really do have two tests that try to refer to the
same line (one of which is an XFAIL), but this breaks the summary reporter.

Is there a way of reworking this test to remove these bogus reports, perhaps by
duplicating the declarations on separate lines so instead of:

void f (int[n1][2][n3][4][n5][6][*][8][n9]);   // { dg-warning "argument 1 of
type 'int\\\[n1]\\\[2]\\\[n3]\\\[4]\\\[n5]\\\[6]\\\[\\\*]\\\[8]\\\[n9]'
declared with 1 unspecified variable bound" "pr?????" { xfail *-*-* } }
// { dg-warning "argument 1 of type
'int\\\[n1]\\\[2]\\\[n3]\\\[4]\\\[n5]\\\[6]\\\[0]\\\[8]\\\[n9]' declared with 1
unspecified variable bound" "pr?????" { target *-*-* } .-1 }


We have:

void f (int[n1][2][n3][4][n5][6][*][8][n9]);   // { dg-warning "argument 1 of
type 'int\\\[n1]\\\[2]\\\[n3]\\\[4]\\\[n5]\\\[6]\\\[\\\*]\\\[8]\\\[n9]'
declared with 1 unspecified variable bound" "pr?????" { xfail *-*-* } }
void g (int[n1][2][n3][4][n5][6][*][8][n9]);  // { dg-warning "argument 1 of
type 'int\\\[n1]\\\[2]\\\[n3]\\\[4]\\\[n5]\\\[6]\\\[0]\\\[8]\\\[n9]' declared
with 1 unspecified variable bound" "pr?????" { target *-*-* } }

             reply	other threads:[~2021-05-04 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 10:50 rearnsha at gcc dot gnu.org [this message]
2021-05-04 11:57 ` [Bug c++/100412] " schwab@linux-m68k.org
2021-05-04 14:49 ` rearnsha at gcc dot gnu.org
2021-05-04 15:17 ` msebor at gcc dot gnu.org
2021-05-04 16:24 ` [Bug testsuite/100412] " msebor at gcc dot gnu.org
2021-08-30 21:41 ` pinskia at gcc dot gnu.org
2022-11-28 22:54 ` pinskia 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-100412-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).