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 tree-optimization/113622] [11/12/13/14 Regression] ICE with vectors in named registers
Date: Mon, 29 Jan 2024 13:31:15 +0000 [thread overview]
Message-ID: <bug-113622-4-LjdOZlZ9YH@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 #18 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:0f7945417f913c85bd556904c0c4e7bf77793488
commit r14-8498-g0f7945417f913c85bd556904c0c4e7bf77793488
Author: Richard Biener <rguenther@suse.de>
Date: Mon Jan 29 10:24:39 2024 +0100
middle-end/113622 - handle store with variable index to register
The following implements storing to a non-MEM_P with a variable
offset. We usually avoid this by forcing expansion to memory but
this doesn't work for hard register variables. The solution is
to spill and operate on the stack.
PR middle-end/113622
* expr.cc (expand_assignment): Spill hard registers if
we index them with a variable offset.
* gcc.target/i386/pr113622-2.c: New testcase.
* gcc.target/i386/pr113622-3.c: Likewise.
next prev parent reply other threads:[~2024-01-29 13:31 UTC|newest]
Thread overview: 28+ 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
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 [this message]
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
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-LjdOZlZ9YH@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).