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/108120] [11/12 Regression] ICE: in extract_insn, at recog.cc:2791 (on ARM with -mfpu=neon -freciprocal-math -O3)
Date: Fri, 23 Feb 2024 13:53:52 +0000	[thread overview]
Message-ID: <bug-108120-4-FvdoiBY1Ds@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108120-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Earnshaw
<rearnsha@gcc.gnu.org>:

https://gcc.gnu.org/g:0de82d2c2ec0b7ed65a1122884feab40f90c0483

commit r12-10174-g0de82d2c2ec0b7ed65a1122884feab40f90c0483
Author: Richard Earnshaw <rearnsha@arm.com>
Date:   Thu Feb 22 16:47:20 2024 +0000

    arm: fix ICE with vectorized reciprocal division [PR108120]

    The expand pattern for reciprocal division was enabled for all math
    optimization modes, but the patterns it was generating were not
    enabled unless -funsafe-math-optimizations were enabled, this leads to
    an ICE when the pattern we generate cannot be recognized.

    Fixed by only enabling vector division when doing unsafe math.

    gcc:

            PR target/108120
            * config/arm/neon.md (div<VCVTF:mode>3): Rename from div<mode>3.
            Gate with ARM_HAVE_NEON_<MODE>_ARITH.

    gcc/testsuite:
            PR target/108120
            * gcc.target/arm/neon-recip-div-1.c: New file.

    (cherry picked from commit 016c4eed368b80a97101f6156ed99e4c5474fbb7)

  parent reply	other threads:[~2024-02-23 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  8:13 [Bug c/108120] New: " m.olbrich at pengutronix dot de
2022-12-15  8:33 ` [Bug target/108120] [11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-12-15  8:33 ` [Bug target/108120] [10/11/12/13 " pinskia at gcc dot gnu.org
2022-12-21 12:43 ` rguenth at gcc dot gnu.org
2023-07-07 10:44 ` [Bug target/108120] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-02-23 11:41 ` cvs-commit at gcc dot gnu.org
2024-02-23 11:43 ` [Bug target/108120] [11/12/13 " rearnsha at gcc dot gnu.org
2024-02-23 12:45 ` cvs-commit at gcc dot gnu.org
2024-02-23 12:46 ` [Bug target/108120] [11/12 " rearnsha at gcc dot gnu.org
2024-02-23 13:53 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-23 13:54 ` cvs-commit at gcc dot gnu.org
2024-02-23 13:55 ` rearnsha 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-108120-4-FvdoiBY1Ds@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).