public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111319] Wrong code at -O2 on x86_64-linux-gnu
Date: Thu, 07 Sep 2023 08:01:12 +0000	[thread overview]
Message-ID: <bug-111319-4-F9DUSiHC5f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111319-4@http.gcc.gnu.org/bugzilla/>

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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
                 CC|                            |xry111 at gcc dot gnu.org
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Please try not to create more reports with "not sure if there is UB" esp. this
UB should be obvious, and it's also detectable with -fsanitize=undefined:

t.c:13:7: runtime error: load of address 0x7ffd53183020 with insufficient space
for an object of type 'int'
0x7ffd53183020: note: pointer points here
 2a 56 00 00  01 00 00 00 00 00 00 00  00 14 1a ed ca 50 d4 0e  00 00 00 00 00
00 00 00  98 31 18 53
              ^

  parent reply	other threads:[~2023-09-07  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07  7:38 [Bug c/111319] New: " shaohua.li at inf dot ethz.ch
2023-09-07  7:40 ` [Bug c/111319] " pinskia at gcc dot gnu.org
2023-09-07  7:59 ` pinskia at gcc dot gnu.org
2023-09-07  8:01 ` xry111 at gcc dot gnu.org [this message]
2023-09-07  8:09 ` shaohua.li at inf dot ethz.ch

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-111319-4-F9DUSiHC5f@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).