public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100200] [10/11/12 Regression] UB evaluating aarch64_plus_immediate predicate
Date: Tue, 27 Apr 2021 13:57:03 +0000 [thread overview]
Message-ID: <bug-100200-4-ePYfFrTGB3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100200-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100200
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:3fe1c1fd0eb5e4bbc1af313b3e9dd4605ec5a134
commit r11-8301-g3fe1c1fd0eb5e4bbc1af313b3e9dd4605ec5a134
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Apr 27 15:46:16 2021 +0200
aarch64: Fix UB in the compiler [PR100200]
The following patch fixes UBs in the compiler when negativing
a CONST_INT containing HOST_WIDE_INT_MIN. I've changed the spots where
there wasn't an obvious earlier condition check or predicate that
would fail for such CONST_INTs.
2021-04-27 Jakub Jelinek <jakub@redhat.com>
PR target/100200
* config/aarch64/predicates.md (aarch64_sub_immediate,
aarch64_plus_immediate): Use -UINTVAL instead of -INTVAL.
* config/aarch64/aarch64.md (casesi, rotl<mode>3): Likewise.
* config/aarch64/aarch64.c (aarch64_print_operand,
aarch64_split_atomic_op, aarch64_expand_subvti): Likewise.
(cherry picked from commit 618ae596ebcd1de03857d20485d1324931852569)
next prev parent reply other threads:[~2021-04-27 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 9:21 [Bug target/100200] New: " acoplan at gcc dot gnu.org
2021-04-22 9:42 ` [Bug target/100200] " acoplan at gcc dot gnu.org
2021-04-22 10:01 ` acoplan at gcc dot gnu.org
2021-04-22 10:34 ` rguenth at gcc dot gnu.org
2021-04-26 14:47 ` jakub at gcc dot gnu.org
2021-04-27 13:46 ` cvs-commit at gcc dot gnu.org
2021-04-27 13:57 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-27 13:59 ` [Bug target/100200] [10 " jakub at gcc dot gnu.org
2021-04-27 15:52 ` cvs-commit at gcc dot gnu.org
2021-04-27 15:53 ` cvs-commit at gcc dot gnu.org
2022-06-28 10:44 ` jakub at gcc dot gnu.org
2023-07-07 9:37 ` rguenth 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-100200-4-ePYfFrTGB3@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).