public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96762] ICE in extract_insn, at recog.c:2294 (error: unrecognizable insn) Date: Thu, 27 May 2021 20:26:42 +0000 [thread overview] Message-ID: <bug-96762-4-RLmkS7SBg9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96762-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96762 Michael Meissner <meissner at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-05-27 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |meissner at gcc dot gnu.org --- Comment #1 from Michael Meissner <meissner at gcc dot gnu.org> --- The example only shows the bug with big endian, 32-bit without optimization. If you optimize the code, the array assignment goes away. Here is a better example that can be optimized: extern void foo (char *); void g4 (void) { char zj[] = "XXXXXXXXXXXXXXXX"; foo (zj); } With the current trunk (as of May 27th) the new example fails at no optimization, -O1, and -O2.
next prev parent reply other threads:[~2021-05-27 20:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-24 9:33 [Bug target/96762] New: " asolokha at gmx dot com 2021-05-27 20:26 ` meissner at gcc dot gnu.org [this message] 2021-05-29 18:23 ` [Bug target/96762] " meissner at gcc dot gnu.org 2021-05-29 19:53 ` segher at gcc dot gnu.org 2023-06-02 3:02 ` bergner at gcc dot gnu.org 2023-08-30 2:31 ` linkw at gcc dot gnu.org 2023-08-31 5:44 ` cvs-commit at gcc dot gnu.org 2023-09-12 1:54 ` cvs-commit at gcc dot gnu.org 2023-09-12 1:56 ` cvs-commit at gcc dot gnu.org 2023-09-12 1:58 ` cvs-commit at gcc dot gnu.org 2023-09-12 1:59 ` guihaoc 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-96762-4-RLmkS7SBg9@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).