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 middle-end/101457] [12 regression] new test cases in r12-2300 fail
Date: Thu, 15 Jul 2021 16:42:37 +0000	[thread overview]
Message-ID: <bug-101457-4-SMbjSwjv3F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101457-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>:

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

commit r12-2330-gb25edf6e6feeadc6a5aa337b8c725786227162dd
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Thu Jul 15 17:42:10 2021 +0100

    testsuite: Fix testisms in scalar tests PR101457

    These testcases accidentally contain the wrong signs for the expected
values
    for the scalar code.  The vector code however is correct.

    Committed as a trivial fix.

    gcc/testsuite/ChangeLog:

            PR middle-end/101457
            * gcc.dg/vect/vect-reduc-dot-17.c: Fix signs of scalar code.
            * gcc.dg/vect/vect-reduc-dot-18.c: Likewise.
            * gcc.dg/vect/vect-reduc-dot-22.c: Likewise.
            * gcc.dg/vect/vect-reduc-dot-9.c: Likewise.

  parent reply	other threads:[~2021-07-15 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 23:41 [Bug middle-end/101457] New: " seurer at gcc dot gnu.org
2021-07-15  5:55 ` [Bug middle-end/101457] " tnfchris at gcc dot gnu.org
2021-07-15  7:04 ` rguenth at gcc dot gnu.org
2021-07-15 16:42 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-15 16:43 ` tnfchris at gcc dot gnu.org
2021-07-16 14:57 ` cvs-commit 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-101457-4-SMbjSwjv3F@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).