public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/99498] [11 regression] new test case g++.dg/opt/pr99305.C in r11-7587 fails
Date: Wed, 10 Mar 2021 16:41:57 +0000 [thread overview]
Message-ID: <bug-99498-4-2oYP67m0Md@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99498-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99498
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:5bf998275aff311b9804c1de944a88c219f35db6
commit r11-7607-g5bf998275aff311b9804c1de944a88c219f35db6
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Mar 10 17:40:25 2021 +0100
testsuite: Fix up pr99305.C test on unsigned_char targets [PR99498]
On unsigned_char targets, the cast stmt to unsigned char is obviously
not needed (and shouldn't be there). But it doesn't hurt to test
the rest also on targets where char is unsigned.
2021-03-10 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/99305
PR testsuite/99498
* g++.dg/opt/pr99305.C: Don't expect cast to unsigned char on
unsigned_char effective targets.
next prev parent reply other threads:[~2021-03-10 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 22:56 [Bug testsuite/99498] New: " seurer at gcc dot gnu.org
2021-03-10 8:16 ` [Bug testsuite/99498] " rguenth at gcc dot gnu.org
2021-03-10 14:47 ` clyon at gcc dot gnu.org
2021-03-10 16:41 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-10 16:43 ` 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-99498-4-2oYP67m0Md@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).