public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/108991] New: [13 regression] gcc.dg/memchr-3.c fails after r13-6414-g62a8d31ecc0704
Date: Thu, 02 Mar 2023 17:06:06 +0000	[thread overview]
Message-ID: <bug-108991-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108991
           Summary: [13 regression] gcc.dg/memchr-3.c fails after
                    r13-6414-g62a8d31ecc0704
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:62a8d31ecc07041af4a81353c2d57d9845c4b771, r13-6414-g62a8d31ecc0704
make  -k check-gcc RUNTESTFLAGS="dg.exp=gcc.dg/memchr-3.c"
FAIL: gcc.dg/memchr-3.c  target llp64  (test for warnings, line 9)
# of expected passes            1
# of unexpected failures        1


Looks like a missing warning?

spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/memchr-3.c
-fdiagnostics-plain-output -O2 -Wall -S -o memchr-3.s^M
FAIL: gcc.dg/memchr-3.c  target llp64  (test for warnings, line 9)
Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled3864749.cc   
-fdiagnostics-plain-output  -Wno-complain-wrong-lang -S -o
exceptions_enabled3864749.s    (timeout = 300)
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled3864749.cc
-fdiagnostics-plain-output -Wno-complain-wrong-lang -S -o
exceptions_enabled3864749.s^M
PASS: gcc.dg/memchr-3.c (test for excess errors)
testcase /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/dg.exp completed in
0 seconds

                === gcc Summary ===

# of expected passes            1
# of unexpected failures        1


commit 62a8d31ecc07041af4a81353c2d57d9845c4b771 (HEAD)
Author: Jonathan Yong <10walls@gmail.com>
Date:   Mon Feb 27 10:02:32 2023 +0000

    gcc.dg/memchr-3.c: Account for LLP64 warnings

             reply	other threads:[~2023-03-02 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 17:06 seurer at gcc dot gnu.org [this message]
2023-03-02 23:51 ` [Bug testsuite/108991] " cvs-commit at gcc dot gnu.org
2023-03-02 23:53 ` jakub 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-108991-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).