public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xen0n at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/112476] New: [14 Regression] unrecognizable insn with -O2 -march=la464 on loongarch64
Date: Fri, 10 Nov 2023 11:58:22 +0000	[thread overview]
Message-ID: <bug-112476-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112476

            Bug ID: 112476
           Summary: [14 Regression] unrecognizable insn with -O2
                    -march=la464 on loongarch64
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: xen0n at gentoo dot org
  Target Milestone: ---
            Target: loongarch64-linux-gnu

Created attachment 56551
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56551&action=edit
Minimized reproducer

The attached code minified from Skia, ICEs with "unrecognizable insn" when
compiled with SIMD apparently active and the backend wanting to do something
with it.

According to my preliminary debugging: the bug disappears when the extra layer
of wrapping function is removed, when the two "&a" arguments get changed, and
when the memcpy is rewritten to a simple pointer dereference.

             reply	other threads:[~2023-11-10 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 11:58 xen0n at gentoo dot org [this message]
2023-11-10 13:41 ` [Bug rtl-optimization/112476] Unrecognizable " xry111 at gcc dot gnu.org
2023-11-11 10:32 ` xry111 at gcc dot gnu.org
2023-11-11 11:08 ` xry111 at gcc dot gnu.org
2023-11-11 16:49 ` [Bug target/112476] " xry111 at gcc dot gnu.org
2023-11-12  1:02 ` xry111 at gcc dot gnu.org
2023-11-13  6:16 ` cvs-commit at gcc dot gnu.org
2023-11-13  6:22 ` xry111 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-112476-4@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).