public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.smets at nokia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100653] New: usage of scalar_storage_order produces incorrect result
Date: Tue, 18 May 2021 15:23:16 +0000	[thread overview]
Message-ID: <bug-100653-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100653
           Summary: usage of scalar_storage_order produces incorrect
                    result
           Product: gcc
           Version: 11.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jan.smets at nokia dot com
  Target Milestone: ---

Created attachment 50840
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50840&action=edit
scalar_storage_order test case

Attached test case produces invalid results with -O2, good with -O1.

Known to fail : 11.1 10.3 9.3 8.5 7.5
Known to work: 6.5 
Target: x86_64-linux-gnu

$ gcc test.c -o /tmp/test -O2 -Wall -Wextra && /tmp/test
a0a1e01 EQ? 11e0a0a 0
$ gcc test.c -o /tmp/test -O1 -Wall -Wextra && /tmp/test
a0a1e01 EQ? a0a1e01 1

Thank you

             reply	other threads:[~2021-05-18 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 15:23 jan.smets at nokia dot com [this message]
2021-05-19  1:14 ` [Bug tree-optimization/100653] " pinskia at gcc dot gnu.org
2021-05-26 10:49 ` ebotcazou at gcc dot gnu.org
2021-05-26 12:36 ` jan.smets at nokia dot com
2021-05-26 12:45 ` ebotcazou at gcc dot gnu.org
2021-05-26 13:04 ` ebotcazou at gcc dot gnu.org
2021-05-26 17:14 ` [Bug c/100653] " cvs-commit at gcc dot gnu.org
2021-05-26 22:26 ` cvs-commit at gcc dot gnu.org
2021-05-27 19:29 ` pinskia at gcc dot gnu.org
2021-06-15 15:49 ` george.thopas at gmail dot com
2021-06-15 16:42 ` ebotcazou 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-100653-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).