public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph.weening at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110227] New: gcc generates invalid AVX-512 code
Date: Mon, 12 Jun 2023 14:47:58 +0000	[thread overview]
Message-ID: <bug-110227-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110227
           Summary: gcc generates invalid AVX-512 code
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: joseph.weening at gmail dot com
  Target Milestone: ---

gcc version 13.1.0 (GCC)
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-13.1.0/configure --prefix=/usr/local/gcc/13.1.0
--disable-multilib --enable-languages=c,c++,fortran
--with-gmp=/usr/local/gmp/6.2.1 --with-mpc=/usr/local/mpc/1.3.1
--with-mpfr=/usr/local/mpfr/4.2.0 --with-isl=/usr/local/isl/0.24

The following program generates an error:
  /tmp/ccAuHFqz.s: Assembler messages:
  /tmp/ccAuHFqz.s:28: Error: unsupported instruction `vpcmpeqd'
The assembly code contains
        vpcmpeqd         %xmm16, %xmm16, %xmm16
which perhaps is invalid for xmm registers above 15.

#include <immintrin.h>

__attribute__((noinline))
static void vswap(int32_t *x) {
  __m256i x0 = _mm256_loadu_si256((__m256i *) (&x[0]));
  __m256i x1 = _mm256_loadu_si256((__m256i *) (&x[1]));
  _mm256_storeu_si256((__m256i *) (&x[0]),(x1));
  _mm256_storeu_si256((__m256i *) (&x[1]),(x0));
}

void vproc(int32_t *x) {
  for (int32_t p=4; p>=1; p>>=1) {
    if (p == 4) {
      __m256i mask = _mm256_set_epi32(0, 0, 0, 0, -1, -1, -1, -1);
      __m256i x0 = _mm256_loadu_si256((__m256i *) (&x[0]));
      x0 = _mm256_xor_si256(x0, mask);
      _mm256_storeu_si256((__m256i *) (&x[0]),(x0));
    }
    vswap(x);
  }
}

             reply	other threads:[~2023-06-12 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 14:47 joseph.weening at gmail dot com [this message]
2023-06-12 14:51 ` [Bug target/110227] " joseph.weening at gmail dot com
2023-06-12 15:43 ` [Bug target/110227] [13/14 Regression] " pinskia at gcc dot gnu.org
2023-06-13  3:06 ` crazylht at gmail dot com
2023-06-13 11:41 ` jakub at gcc dot gnu.org
2023-06-13 13:55 ` rguenth at gcc dot gnu.org
2023-06-14  8:19 ` cvs-commit at gcc dot gnu.org
2023-06-14  8:20 ` cvs-commit at gcc dot gnu.org
2023-06-14  8:21 ` crazylht at gmail dot com
2023-07-27  9:26 ` rguenth at gcc dot gnu.org
2023-11-30 10:54 ` liuhongt 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-110227-4@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).