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/107830] [13 Regression] ICE in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813 Date: Fri, 25 Nov 2022 12:58:09 +0000 [thread overview] Message-ID: <bug-107830-4-cBTKcs9NDU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107830-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107830 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>: https://gcc.gnu.org/g:71f3036b8a83da7fb559923bc80687ea1dabe14a commit r13-4303-g71f3036b8a83da7fb559923bc80687ea1dabe14a Author: Tamar Christina <tamar.christina@arm.com> Date: Fri Nov 25 12:57:24 2022 +0000 sve2: Fix expansion of division [PR107830] SVE has an actual division optab, and when using -Os we don't optimize the division away. This means that we need to distinguish between a div which we can optimize and one we cannot even during expansion. gcc/ChangeLog: PR target/107830 * config/aarch64/aarch64.cc (aarch64_vectorize_can_special_div_by_constant): Check validity during codegen phase as well. gcc/testsuite/ChangeLog: PR target/107830 * gcc.target/aarch64/sve2/pr107830-1.c: New test. * gcc.target/aarch64/sve2/pr107830-2.c: New test.
next prev parent reply other threads:[~2022-11-25 12:58 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-23 3:54 [Bug testsuite/107830] New: " asolokha at gmx dot com 2022-11-23 10:11 ` [Bug target/107830] " marxin at gcc dot gnu.org 2022-11-23 10:43 ` ktkachov at gcc dot gnu.org 2022-11-23 10:53 ` tnfchris at gcc dot gnu.org 2022-11-23 20:54 ` rguenth at gcc dot gnu.org 2022-11-25 12:58 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-25 12:59 ` tnfchris 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-107830-4-cBTKcs9NDU@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).