public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113415] ICE: RTL check: -mstringop-strategy=byte_loop vs inline-asm goto with block copies
Date: Thu, 08 Feb 2024 17:54:48 +0000 [thread overview]
Message-ID: <bug-113415-4-2BMBDBXlMO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113415-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113415
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 57364
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57364&action=edit
gcc14-pr113415.patch
If all we care here is not to ICE on it, then this patch should suffice.
But, if there is some asm goto where such loops could be emitted and needed on
all the asm goto edges, then more work will be needed,
duplicate_insn_chain doesn't duplicate CODE_LABELs and remap references to them
in the copied sequences.
next prev parent reply other threads:[~2024-02-08 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 5:46 [Bug rtl-optimization/113415] New: ICE: RTL check: expected elt 3 type 'e' or 'u', have '0' (rtx code_label) in PATTERN, at rtl.h:1511 with -mstringop-strategy=byte_loop and invalid __asm__ on _BitInt() zsojka at seznam dot cz
2024-01-16 6:00 ` [Bug middle-end/113415] " pinskia at gcc dot gnu.org
2024-01-16 6:07 ` [Bug middle-end/113415] ICE: RTL check: -mstringop-strategy=byte_loop vs inline-asm goto with block copies pinskia at gcc dot gnu.org
2024-01-18 23:03 ` pinskia at gcc dot gnu.org
2024-01-18 23:05 ` pinskia at gcc dot gnu.org
2024-02-07 21:33 ` pinskia at gcc dot gnu.org
2024-02-08 17:54 ` jakub at gcc dot gnu.org [this message]
2024-02-09 10:09 ` cvs-commit at gcc dot gnu.org
2024-02-09 10:13 ` jakub at gcc dot gnu.org
2024-02-14 17:25 ` 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-113415-4-2BMBDBXlMO@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).