public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vsevolod.livinskiy at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105621] New: [13 Regression] Wrong code with -O3
Date: Mon, 16 May 2022 19:03:58 +0000	[thread overview]
Message-ID: <bug-105621-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105621
           Summary: [13 Regression] Wrong code with -O3
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vsevolod.livinskiy at gmail dot com
  Target Milestone: ---

Link to the Compiler Explorer: https://godbolt.org/z/jscK4bTP6

Reproducer:
#include <stdio.h>

unsigned short a = (unsigned short)31272;
int b = -1902905271;
unsigned int c = 1618489477U;
bool d = (bool)0;

void test(unsigned short a, int b, unsigned c) __attribute__((noipa));
void test(unsigned short a, int b, unsigned c) {
  for (int i = 2; i < 24; i += 3)
    d = b ? a ? c : 2086607777901731118 : 0; 
}

int main() {
    test(a, b, c);
    printf("%d\n", (int)d);
    if (d != 1)
      __builtin_abort();
}

Error:
>$ g++ -O2 driver.cpp && ./a.out 
1
>$ g++ -O3 driver.cpp && ./a.out 
0
Aborted (core dumped)

GCC version 13.0.0 20220516 (69c4b5c519f0df37e4903992644cc29682721bc1)

             reply	other threads:[~2022-05-16 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 19:03 vsevolod.livinskiy at gmail dot com [this message]
2022-05-17  6:58 ` [Bug tree-optimization/105621] " rguenth at gcc dot gnu.org
2022-05-17 10:50 ` marxin 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-105621-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).