public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "652023330028 at smail dot nju.edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113271] [Regression] Wrong code at -O1/2/3 since GCC-9 (could be due to wrong optimization)
Date: Tue, 09 Jan 2024 06:27:34 +0000	[thread overview]
Message-ID: <bug-113271-4-z5pc5ukysi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113271-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Yi <652023330028 at smail dot nju.edu.cn> ---
(In reply to Xi Ruoyao from comment #2)
> -fsanitize=undefined is even explicitly mentioned in the bug report
> guideline at https://gcc.gnu.org/bugs/.  And the red banner in the new bug
> page also mentions -fwrapv.

I'm sorry about this issue. I knew what you mentioned. I seemed a little out of
my mind when I brought up the issue.



(In reply to Jakub Jelinek from comment #1)
> This is UB, as can be seen if you compile with -fsanitize=undefined:

I'm sorry again.

      parent reply	other threads:[~2024-01-09  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 12:08 [Bug tree-optimization/113271] New: " 652023330028 at smail dot nju.edu.cn
2024-01-08 12:16 ` [Bug tree-optimization/113271] " jakub at gcc dot gnu.org
2024-01-09  6:14 ` xry111 at gcc dot gnu.org
2024-01-09  6:27 ` 652023330028 at smail dot nju.edu.cn [this message]

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-113271-4-z5pc5ukysi@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).