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 other/106575] new test case gcc.dg/fold-eqandshift-4.c fails with its introduction in r13-2005-g6fc14f1963dfef
Date: Wed, 10 Aug 2022 06:08:06 +0000	[thread overview]
Message-ID: <bug-106575-4-8SNtE3iSWQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106575-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:c16d9f78dc81664e3341157c5a6efb85c0c141f4

commit r13-2009-gc16d9f78dc81664e3341157c5a6efb85c0c141f4
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Wed Aug 10 07:05:33 2022 +0100

    [Committed] PR other/106575: Use "signed char" in new fold-eqandshift-4.c

    My recently added testcase gcc.dg/fold-eqandshift-4.c, incorrectly assumed
    that "char" was "signed char", and hence fails on powerpc64 where this
    isn't the case.  Fixed by making "signed char" explicit where needed in
    this test.  Committed as obvious.

    2022-08-10  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/testsuite/ChangeLog
            PR other/106575
            * gcc.dg/fold-eqandshift-4.c: Use "signed char" explicitly.

  reply	other threads:[~2022-08-10  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10  3:48 [Bug other/106575] New: new test case gcc.dg/fold-eqandshift-4.c fails seurer at gcc dot gnu.org
2022-08-10  6:08 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-10  7:25 ` [Bug other/106575] new test case gcc.dg/fold-eqandshift-4.c fails with its introduction in r13-2005-g6fc14f1963dfef rguenth 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-106575-4-8SNtE3iSWQ@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).