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/105486] new test case gcc.dg/vect/bb-slp-pr104240.c from  r13-71-g41e3db05d69740
Date: Thu, 05 May 2022 12:31:23 +0000	[thread overview]
Message-ID: <bug-105486-4-UIZinukyli@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105486-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 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:92fff39f06449f907d8781a5dcaad0e8b9743480

commit r13-136-g92fff39f06449f907d8781a5dcaad0e8b9743480
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Thu May 5 08:30:27 2022 -0400

    [Committed] PR testsuite/105486: Use "signed char" in gcc.dg/pr102950.c

    Although the automated regression testing scripts for powerpc64 appear
    to be somewhat garbled at the moment, they've correctly identified that
    my new test case for pr102950.c is failing on powerpc64, as char by
    default is unsigned on this target.  This patch tweaks the new testcase
    by explicitly using "signed char" so that it's testing the intended EVRP
    behaviour portably.  Committed as obvious.

    2022-05-05  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/testsuite/ChangeLog
            PR testsuite/105486
            * gcc.dg/pr102950.c: Use explicit "signed char" in test case.

  parent reply	other threads:[~2022-05-05 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 21:07 [Bug testsuite/105486] New: new test case gcc.dg/vect/bb-slp-pr104240.c from r13-89-gb3e98eb3396e16 fails seurer at gcc dot gnu.org
2022-05-05  7:16 ` [Bug testsuite/105486] new test case gcc.dg/vect/bb-slp-pr104240.c from r13-71-g41e3db05d69740 rguenth at gcc dot gnu.org
2022-05-05  8:42 ` cvs-commit at gcc dot gnu.org
2022-05-05  8:43 ` rguenth at gcc dot gnu.org
2022-05-05 10:08 ` roger at nextmovesoftware dot com
2022-05-05 12:31 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-07 20:04 ` roger at nextmovesoftware dot com

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-105486-4-UIZinukyli@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).