public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113622] [11/12/13/14 Regression] ICE with vectors in named registers Date: Fri, 26 Jan 2024 20:59:40 +0000 [thread overview] Message-ID: <bug-113622-4-vfsT68oqHS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113622-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The assert by the way: ``` if (!MEM_P (to_rtx)) { /* We can get constant negative offsets into arrays with broken user code. Translate this to a trap instead of ICEing. */ gcc_assert (TREE_CODE (offset) == INTEGER_CST); expand_builtin_trap (); to_rtx = gen_rtx_MEM (BLKmode, const0_rtx); } ``` Yes this is obvious is wrong when used with global registers ...
next prev parent reply other threads:[~2024-01-26 20:59 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-26 20:16 [Bug tree-optimization/113622] New: r14-8450 regression: " xry111 at gcc dot gnu.org 2024-01-26 20:23 ` [Bug tree-optimization/113622] " xry111 at gcc dot gnu.org 2024-01-26 20:31 ` [Bug tree-optimization/113622] " pinskia at gcc dot gnu.org 2024-01-26 20:36 ` xry111 at gcc dot gnu.org 2024-01-26 20:39 ` [Bug tree-optimization/113622] [11/12/13/14 Regression] " jakub at gcc dot gnu.org 2024-01-26 20:43 ` pinskia at gcc dot gnu.org 2024-01-26 20:59 ` pinskia at gcc dot gnu.org [this message] 2024-01-27 3:49 ` pinskia at gcc dot gnu.org 2024-01-27 12:11 ` jakub at gcc dot gnu.org 2024-01-29 7:56 ` rguenth at gcc dot gnu.org 2024-01-29 8:45 ` rguenth at gcc dot gnu.org 2024-01-29 8:56 ` jakub at gcc dot gnu.org 2024-01-29 8:58 ` xry111 at gcc dot gnu.org 2024-01-29 9:07 ` jakub at gcc dot gnu.org 2024-01-29 9:09 ` xry111 at gcc dot gnu.org 2024-01-29 9:27 ` rguenth at gcc dot gnu.org 2024-01-29 9:38 ` rguenth at gcc dot gnu.org 2024-01-29 13:31 ` cvs-commit at gcc dot gnu.org 2024-01-29 13:31 ` cvs-commit at gcc dot gnu.org 2024-01-29 13:32 ` [Bug tree-optimization/113622] [11/12/13 " rguenth at gcc dot gnu.org 2024-01-30 8:34 ` cvs-commit at gcc dot gnu.org 2024-01-30 13:22 ` xry111 at gcc dot gnu.org 2024-01-30 13:27 ` xry111 at gcc dot gnu.org 2024-01-30 14:49 ` rguenther at suse dot de 2024-02-25 13:08 ` xry111 at gcc dot gnu.org 2024-03-21 13:54 ` cvs-commit at gcc dot gnu.org 2024-03-21 13:57 ` rguenth at gcc dot gnu.org 2024-05-06 11:49 ` rguenth at gcc dot gnu.org 2024-07-19 13:23 ` [Bug tree-optimization/113622] [12/13 " 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-113622-4-vfsT68oqHS@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).