public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: gcc-patches@gcc.gnu.org, Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: [PATCH] testsuite: Fix gcc.dg/vect/vect-fmax-1.c etc. on SPARC [PR104756]
Date: Mon, 23 Jan 2023 13:41:14 +0100	[thread overview]
Message-ID: <CAFiYyc102FbyijkujMh8RVHM4UW4MS5p_R7XHrBPxwKnPAmEFA@mail.gmail.com> (raw)
In-Reply-To: <yddr0vltu0v.fsf@CeBiTec.Uni-Bielefeld.DE>

On Mon, Jan 23, 2023 at 11:39 AM Rainer Orth
<ro@cebitec.uni-bielefeld.de> wrote:
>
> The gcc.dg/vect/vect-fmax-?.c etc. tests FAIL on 32 and 64-bit SPARC:
>
> FAIL: gcc.dg/vect/vect-fmax-1.c -flto -ffat-lto-objects  scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmax-1.c scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmax-2.c -flto -ffat-lto-objects  scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmax-2.c scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmax-3.c -flto -ffat-lto-objects  scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmax-3.c scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmin-1.c -flto -ffat-lto-objects  scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmin-1.c -flto -ffat-lto-objects  scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmin-1.c scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmin-1.c scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmin-2.c -flto -ffat-lto-objects  scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmin-2.c scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmin-3.c -flto -ffat-lto-objects  scan-tree-dump vect "Detected reduction"
> FAIL: gcc.dg/vect/vect-fmin-3.c scan-tree-dump vect "Detected reduction"
>
> As discussed in the PR, they require vect_float support, but the tests
> don't declare it.
>
> This patch fixes this.
>
> Tested on sparc-sun-solaris2.11 and i386-pc-solaris2.11.
>
> Ok for trunk?

OK.

>         Rainer
>
> --
> -----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University
>
>
> 2023-01-20  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
>
>         gcc/testsuite:
>         PR testsuite/104756
>         * gcc.dg/vect/vect-fmax-1.c: Require vect_float.
>         * gcc.dg/vect/vect-fmax-2.c: Likewise.
>         * gcc.dg/vect/vect-fmax-3.c: Likewise.
>         * gcc.dg/vect/vect-fmin-1.c: Likewise.
>         * gcc.dg/vect/vect-fmin-2.c: Likewise.
>         * gcc.dg/vect/vect-fmin-3.c: Likewise.
>

      reply	other threads:[~2023-01-23 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 10:38 Rainer Orth
2023-01-23 12:41 ` Richard Biener [this message]

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=CAFiYyc102FbyijkujMh8RVHM4UW4MS5p_R7XHrBPxwKnPAmEFA@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdsandiford@googlemail.com \
    --cc=ro@cebitec.uni-bielefeld.de \
    /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).