public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107131] [11/12/13 Regression] wrong code with -Os -fno-ipa-vrp -fno-tree-bit-ccp
Date: Fri, 13 Jan 2023 14:01:21 +0000	[thread overview]
Message-ID: <bug-107131-4-x8bDq7BHff@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107131-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If I change the testcase to:
/* PR target/107131 */
/* { dg-do run } */
/* { dg-options "-Os -fno-ipa-vrp -fno-tree-bit-ccp -Wno-psabi" } */

typedef unsigned char C;
typedef unsigned long long __attribute__((__vector_size__ (32))) U;
typedef unsigned long long __attribute__((__vector_size__ (64))) V;

static __attribute__((__noclone__)) C
foo (C o, U x, U y, U z)
{
  V w = { x[0], x[1], x[2], x[3], 0, 0, 0, 0 };
  V a = __builtin_shuffle (w, w, (V) {3, 1, 3, 0, 0, 1, 1, 3});
  V b = (V) { } >= o;
  V c = b <= (V)(b >= (V) { 0, 0, 0, 0, 0, 0x90DF0BE3990AC871ULL });
  U d = __builtin_shuffle (y, z, (U) {3, 1, 4, 5});
  V e = a + c;
  U f = ((union { V v; U u[2]; }) e).u[1] + d;
  return ((union { U u; C c[32]; }) f).c[9];
}

int
main ()
{
  if (__SIZEOF_LONG_LONG__ != 8 || __CHAR_BIT__ != 8)
    return 0;
  C x = foo (0, (U) { }, (U) { }, (U) { });
  if (x != 0xff)
    __builtin_abort();  
  return 0;
}
then it started with r12-1055-gb6bdd7a4cb41ee057f2d064fffcb00f23ce6b497
already,
but similarly to the other testcase got fixed or made latent with
r13-3217.

  parent reply	other threads:[~2023-01-13 14:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 13:37 [Bug target/107131] New: " zsojka at seznam dot cz
2022-10-03 14:48 ` [Bug target/107131] [11/12 Regression] " marxin at gcc dot gnu.org
2022-10-03 19:34 ` pinskia at gcc dot gnu.org
2022-10-03 19:40 ` pinskia at gcc dot gnu.org
2022-10-06  7:12 ` [Bug target/107131] [11/12/13 " rguenth at gcc dot gnu.org
2022-10-18  8:38 ` rguenth at gcc dot gnu.org
2022-11-18 12:52 ` jakub at gcc dot gnu.org
2023-01-13 10:15 ` cvs-commit at gcc dot gnu.org
2023-01-13 14:01 ` jakub at gcc dot gnu.org [this message]
2023-01-13 16:27 ` jakub at gcc dot gnu.org
2023-01-13 16:39 ` cvs-commit at gcc dot gnu.org
2023-01-13 16:42 ` [Bug target/107131] [11/12 " jakub at gcc dot gnu.org
2023-04-27 12:02 ` rguenth at gcc dot gnu.org
2023-04-27 12:03 ` rguenth at gcc dot gnu.org
2023-05-29 10:07 ` jakub 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-107131-4-x8bDq7BHff@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).