public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at mengyan1223 dot wang" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/104843] signed overflow in compute_const_anchors, at cse.cc:1180
Date: Tue, 08 Mar 2022 18:04:24 +0000 [thread overview]
Message-ID: <bug-104843-4-rmCIE7D8bJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104843-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104843
Xi Ruoyao <xry111 at mengyan1223 dot wang> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |mips
Blocks| |63426
--- Comment #1 from Xi Ruoyao <xry111 at mengyan1223 dot wang> ---
It seems mips is the only target with const_anchor != 0...
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
[Bug 63426] [meta-bug] Issues found with -fsanitize=undefined
next prev parent reply other threads:[~2022-03-08 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 18:03 [Bug rtl-optimization/104843] New: " xry111 at mengyan1223 dot wang
2022-03-08 18:04 ` xry111 at mengyan1223 dot wang [this message]
2023-07-10 20:46 ` [Bug rtl-optimization/104843] " xry111 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-104843-4-rmCIE7D8bJ@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).