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/99540] [10/11 Regression] ICE: Segmentation fault in aarch64_add_offset Date: Tue, 23 Mar 2021 14:02:15 +0000 [thread overview] Message-ID: <bug-99540-4-4tismX7vKx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99540-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99540 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:d7cea7ceff9a2be7436108030c598628c51fba0f commit r11-7787-gd7cea7ceff9a2be7436108030c598628c51fba0f Author: Richard Sandiford <richard.sandiford@arm.com> Date: Tue Mar 23 14:02:03 2021 +0000 aarch64: Make aarch64_add_offset work with -ftrapv [PR99540] aarch64_add_offset uses expand_mult to multiply the SVE VL by an out-of-range constant. expand_mult takes an argument to indicate whether the multiplication is signed or unsigned, but in this context the multiplication is effectively signless and so the choice seemed arbitrary. However, one of the things that the signedness input does is indicate whether signed overflow should be trapped for -ftrapv. We don't want that here, so we must treat the multiplication as unsigned. gcc/ 2021-03-23 Jakub Jelinek <jakub@redhat.com> PR target/99540 * config/aarch64/aarch64.c (aarch64_add_offset): Tell expand_mult to perform an unsigned rather than a signed multiplication. gcc/testsuite/ 2021-03-23 Richard Sandiford <richard.sandiford@arm.com> PR target/99540 * gcc.dg/vect/pr99540.c: New test.
next prev parent reply other threads:[~2021-03-23 14:02 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-11 4:31 [Bug target/99540] New: " asolokha at gmx dot com 2021-03-11 9:00 ` [Bug target/99540] [10/11 Regression] " ktkachov at gcc dot gnu.org 2021-03-11 17:13 ` acoplan at gcc dot gnu.org 2021-03-19 11:58 ` acoplan at gcc dot gnu.org 2021-03-19 12:03 ` jakub at gcc dot gnu.org 2021-03-19 12:05 ` jakub at gcc dot gnu.org 2021-03-19 12:37 ` jakub at gcc dot gnu.org 2021-03-19 12:37 ` jakub at gcc dot gnu.org 2021-03-19 12:43 ` rsandifo at gcc dot gnu.org 2021-03-23 14:02 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-24 19:19 ` [Bug target/99540] [10 " cvs-commit at gcc dot gnu.org 2021-03-30 15:34 ` rsandifo at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-15 16:51 ` acoplan at gcc dot gnu.org 2021-04-15 17:02 ` rsandifo at gcc dot gnu.org 2021-04-23 16:34 ` [Bug target/99540] " rsandifo 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-99540-4-4tismX7vKx@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: linkBe 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).