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/113486] ICE: in extract_insn, at recog.cc:2812 (unrecognizable insn) with -mgeneral-regs-only and __builtin_apply() on aarch64 Date: Wed, 24 Jan 2024 17:50:01 +0000 [thread overview] Message-ID: <bug-113486-4-WIusdEoo7i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113486-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113486 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:d3ff08a3764f2047d02b35212fc4f1da9eb75c7b commit r14-8397-gd3ff08a3764f2047d02b35212fc4f1da9eb75c7b Author: Andrew Pinski <quic_apinski@quicinc.com> Date: Thu Jan 18 10:40:04 2024 -0800 aarch64: Fix __builtin_apply with -mgeneral-regs-only [PR113486] The problem here is the builtin apply mechanism thinks the FP registers are to be used due to get_raw_arg_mode not returning VOIDmode. This fixes that oversight and the backend now returns VOIDmode for non-general-regs if TARGET_GENERAL_REGS_ONLY is true. Built and tested for aarch64-linux-gnu with no regressions. PR target/113486 gcc/ChangeLog: * config/aarch64/aarch64.cc (aarch64_get_reg_raw_mode): For TARGET_GENERAL_REGS_ONLY, return VOIDmode for non-GP_REGNUM_P regno. gcc/testsuite/ChangeLog: * gcc.target/aarch64/builtin_apply-1.c: New test. Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
next prev parent reply other threads:[~2024-01-24 17:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 17:23 [Bug target/113486] New: " zsojka at seznam dot cz 2024-01-18 17:49 ` [Bug target/113486] " pinskia at gcc dot gnu.org 2024-01-18 18:20 ` pinskia at gcc dot gnu.org 2024-01-18 21:58 ` pinskia at gcc dot gnu.org 2024-01-24 17:50 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-24 17:51 ` pinskia 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-113486-4-WIusdEoo7i@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).