public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103271] ICE in assign_stack_temp_for_type with -ftrivial-auto-var-init=pattern and VLAs and -mno-strict-align on riscv64
Date: Fri, 26 Nov 2021 07:16:28 +0000 [thread overview]
Message-ID: <bug-103271-4-juwLZtl37u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103271-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103271
--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 26 Nov 2021, wilson at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103271
>
> Jim Wilson <wilson at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |wilson at gcc dot gnu.org
>
> --- Comment #5 from Jim Wilson <wilson at gcc dot gnu.org> ---
> SiFive doesn't support -mno-strict-align so I've never tested it. I doubt that
> it works correctly, i.e. I doubt that it optimizes as intended. I've mentioned
> this to other RVI members, but there hasn't been anyone other than SiFive
> actively working on upstream gcc so I don't think anyone ever looked at it. It
> shouldn't give an ICE though.
>
> Looking at this, it appears to be another "if only we had a movti pattern"
> issue.
>
> In expand_DEFERRED_INIT in internal-fn.c, in the reg_lhs == TRUE case, there is
> a test
> && have_insn_for (SET, var_mode))
> which fails because var_mode is TImode and we don't have a movti pattern. The
> code calls build_zero_cst which returns a constructor with an array type. We
> then call expand_assignment which gets confused as it doesn't know the size of
> the array it is copying.
That seems to be the bug - in this path we shouldn't ever create an
entity with VLA size since we do know the actual size. But it all
is a bit awkward.
next prev parent reply other threads:[~2021-11-26 7:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 8:55 [Bug target/103271] New: ICE in assign_stack_temp_for_type, at function.c:798 marxin at gcc dot gnu.org
2021-11-16 8:55 ` [Bug target/103271] " marxin at gcc dot gnu.org
2021-11-16 9:39 ` rguenth at gcc dot gnu.org
2021-11-22 23:17 ` [Bug target/103271] ICE in assign_stack_temp_for_type with -ftrivial-auto-var-init=pattern and VLAs and -mno-strict-align on riscv64 qinzhao at gcc dot gnu.org
2021-11-23 7:33 ` marxin at gcc dot gnu.org
2021-11-23 7:47 ` rguenther at suse dot de
2021-11-23 16:22 ` qing.zhao at oracle dot com
2021-11-26 5:08 ` wilson at gcc dot gnu.org
2021-11-26 5:20 ` wilson at gcc dot gnu.org
2021-11-26 7:16 ` rguenther at suse dot de [this message]
2021-12-01 17:17 ` qinzhao at gcc dot gnu.org
2021-12-01 19:46 ` qinzhao at gcc dot gnu.org
2021-12-01 22:31 ` qinzhao at gcc dot gnu.org
2021-12-02 9:07 ` rguenth at gcc dot gnu.org
2021-12-02 9:29 ` rguenth at gcc dot gnu.org
2021-12-02 12:35 ` cvs-commit at gcc dot gnu.org
2021-12-02 12:36 ` rguenth at gcc dot gnu.org
2021-12-02 16:12 ` qinzhao at gcc dot gnu.org
2021-12-02 17:47 ` wilson at gcc dot gnu.org
2021-12-02 22:19 ` qinzhao at gcc dot gnu.org
2021-12-03 23:08 ` wilson 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-103271-4-juwLZtl37u@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).