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/104474] [10/11 Regression] ICE: in output_constant_pool_2, at varasm.cc:4062 with -mcpu=neoverse-512tvb -msve-vector-bits=512 Date: Thu, 07 Apr 2022 09:53:45 +0000 [thread overview] Message-ID: <bug-104474-4-0kEsM0XQDk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104474-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104474 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:b8a6fb4b5919140de74fbc6ad6df1a9caba1c9ec commit r11-9783-gb8a6fb4b5919140de74fbc6ad6df1a9caba1c9ec Author: Andrew Pinski <apinski@marvell.com> Date: Wed Feb 9 14:56:58 2022 -0800 [COMMITTED] Fix PR aarch64/104474: ICE with vector float initializers and non-consts. The problem here is that the aarch64 back-end was placing const0_rtx into the constant vector RTL even if the mode was a floating point mode. The fix is instead to use CONST0_RTX and pass the mode to select the correct zero (either const_int or const_double). Committed as obvious after a bootstrap/test on aarch64-linux-gnu with no regressions. PR target/104474 gcc/ChangeLog: * config/aarch64/aarch64.c (aarch64_sve_expand_vector_init_handle_trailing_constants): Use CONST0_RTX instead of const0_rtx for the non-constant elements. gcc/testsuite/ChangeLog: * gcc.target/aarch64/sve/pr104474-1.c: New test. * gcc.target/aarch64/sve/pr104474-2.c: New test. * gcc.target/aarch64/sve/pr104474-3.c: New test. (cherry picked from commit 41582f88ec01c5ce2f85ebc4ac2743eb426d6e33)
next prev parent reply other threads:[~2022-04-07 9:53 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-09 19:27 [Bug target/104474] New: [12 Regression] ICE: in output_constant_pool_2, at varasm.cc:4062 with -mcpu=neoverse-512tvb -frounding-math -msve-vector-bits=512 zsojka at seznam dot cz 2022-02-09 19:32 ` [Bug target/104474] " pinskia at gcc dot gnu.org 2022-02-09 19:45 ` [Bug target/104474] [12 Regression] ICE: in output_constant_pool_2, at varasm.cc:4062 with -mcpu=neoverse-512tvb -msve-vector-bits=512 pinskia at gcc dot gnu.org 2022-02-09 19:54 ` pinskia at gcc dot gnu.org 2022-02-09 20:00 ` pinskia at gcc dot gnu.org 2022-02-10 0:49 ` cvs-commit at gcc dot gnu.org 2022-02-10 0:53 ` pinskia at gcc dot gnu.org 2022-02-10 9:08 ` [Bug target/104474] [10/11 " pinskia at gcc dot gnu.org 2022-04-07 9:53 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-28 10:48 ` [Bug target/104474] [10 " jakub at gcc dot gnu.org 2023-07-07 9:56 ` 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-104474-4-0kEsM0XQDk@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).