public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drohr at jwdt dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102937] New: Miscompilation with -O3 and aliasing of char* and size_t
Date: Mon, 25 Oct 2021 21:02:08 +0000	[thread overview]
Message-ID: <bug-102937-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102937
           Summary: Miscompilation with -O3 and aliasing of char* and
                    size_t
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: drohr at jwdt dot org
  Target Milestone: ---

Created attachment 51663
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51663&action=edit
testcase

The attached testcase miscompiles with GCC 11.2 when using -O3. It compiles
correctly with -O3, and also with GCC 10.3 using -O3. For reference the code is
also here: https://godbolt.org/z/cjr584sMo

The program prints a ptr twice, which should have been modified in between, but
this is not the case, thus it prints twice a nullptr:
FOO 0x(nil)
BAR 0x(nil)

By either commenting in the printf in line 51 (or also by outcommenting the
call to computePointerWithAlignment in line 50) the miscompilation disappears,
and the output is
FOO 0x(nil)
test 0x800
BAR 0x0x800

             reply	other threads:[~2021-10-25 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 21:02 drohr at jwdt dot org [this message]
2021-10-25 21:17 ` [Bug c++/102937] " pinskia at gcc dot gnu.org
2021-10-25 21:19 ` pinskia at gcc dot gnu.org
2021-10-25 21:44 ` drohr at jwdt dot org
2021-10-25 21:52 ` pinskia 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-102937-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).