public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org,
	Rainer Orth <ro@cebitec.uni-bielefeld.de>,
	 Mike Stump <mikestump@comcast.net>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH] [testsuite] [i386] add -msse2 to tests that require it
Date: Wed, 17 Apr 2024 20:25:18 +0200	[thread overview]
Message-ID: <CAFULd4bCEaHqkY5hT1C2w3QHiO6xpTT+9OE3OaSbBFs+cG9nGg@mail.gmail.com> (raw)
In-Reply-To: <orfrvmc6bq.fsf@lxoliva.fsfla.org>

On Tue, Apr 16, 2024 at 5:52 AM Alexandre Oliva <oliva@adacore.com> wrote:
>
>
> Without -msse2, an i586-targeting toolchain fails bf16_short_warn.c
> because neither type __m128bh nor intrinsic _mm_cvtneps_pbh get
> declared.
>
> Regstrapped on x86_64-linux-gnu.  Also tested with gcc-13 on arm-,
> aarch64-, x86- and x86_64-vxworks7r2.  Ok to install?
>
>
> for  gcc/testsuite/ChangeLog
>
>         * gcc.target/i386/bf16_short_warn.c: Add -msse2.

OK.

Thanks,
Uros.

> ---
>  gcc/testsuite/gcc.target/i386/bf16_short_warn.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.target/i386/bf16_short_warn.c b/gcc/testsuite/gcc.target/i386/bf16_short_warn.c
> index 3e47a815200c2..2e05624bc26f6 100644
> --- a/gcc/testsuite/gcc.target/i386/bf16_short_warn.c
> +++ b/gcc/testsuite/gcc.target/i386/bf16_short_warn.c
> @@ -1,5 +1,5 @@
>  /* { dg-do compile } */
> -/* { dg-options "-O2" } */
> +/* { dg-options "-O2 -msse2" } */
>
>  #include<immintrin.h>
>  typedef struct {
>
> --
> Alexandre Oliva, happy hacker            https://FSFLA.org/blogs/lxo/
>    Free Software Activist                   GNU Toolchain Engineer
> More tolerance and less prejudice are key for inclusion and diversity
> Excluding neuro-others for not behaving ""normal"" is *not* inclusive

      reply	other threads:[~2024-04-17 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16  3:52 Alexandre Oliva
2024-04-17 18:25 ` Uros Bizjak [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=CAFULd4bCEaHqkY5hT1C2w3QHiO6xpTT+9OE3OaSbBFs+cG9nGg@mail.gmail.com \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=mikestump@comcast.net \
    --cc=oliva@adacore.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).