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/105498] New: new test case gcc/testsuite/c-c++-common/Wconversion-1.c from r13-122-g1cd3faf5dddb3c has unexpected errors
Date: Thu, 05 May 2022 20:50:33 +0000 [thread overview]
Message-ID: <bug-105498-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105498
Bug ID: 105498
Summary: new test case
gcc/testsuite/c-c++-common/Wconversion-1.c from
r13-122-g1cd3faf5dddb3c has unexpected errors
Product: gcc
Version: 12.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:1cd3faf5dddb3cbfa2ed308ecf3db4f70bff337e, r13-122-g1cd3faf5dddb3c
make -k check-gcc
RUNTESTFLAGS="dg.exp=gcc/testsuite/c-c++-common/Wconversion-1.c"
# of unexpected failures 1
FAIL: c-c++-common/Wconversion-1.c -Wc++-compat (test for warnings, line 13)
# of unexpected failures 4
FAIL: c-c++-common/Wconversion-1.c -std=gnu++98 (test for warnings, line 13)
FAIL: c-c++-common/Wconversion-1.c -std=gnu++14 (test for warnings, line 13)
FAIL: c-c++-common/Wconversion-1.c -std=gnu++17 (test for warnings, line 13)
FAIL: c-c++-common/Wconversion-1.c -std=gnu++20 (test for warnings, line 13)
commit 1cd3faf5dddb3cbfa2ed308ecf3db4f70bff337e (HEAD, refs/bisect/bad)
Author: Marek Polacek <polacek@redhat.com>
Date: Wed Mar 30 16:59:33 2022 -0400
c-family: Tweak -Woverflow diagnostic
next reply other threads:[~2022-05-05 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 20:50 seurer at gcc dot gnu.org [this message]
2022-05-05 21:00 ` [Bug testsuite/105498] " mpolacek 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-105498-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).