public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch
Date: Sat, 16 Dec 2023 21:35:09 +0000	[thread overview]
Message-ID: <bug-113033-4-Vl5iZDP2fD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113033-4@http.gcc.gnu.org/bugzilla/>

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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization

--- Comment #6 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
There is also a missed-optimization on LoongArch.  vrotlM3 should be expanded
to (rotatert X, (neg Y)) instead of two shifts and an ior.

  parent reply	other threads:[~2023-12-16 21:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 16:44 [Bug target/113033] New: " c at jia dot je
2023-12-16 17:47 ` [Bug target/113033] " xry111 at gcc dot gnu.org
2023-12-16 18:16 ` xry111 at gcc dot gnu.org
2023-12-16 18:32 ` xry111 at gcc dot gnu.org
2023-12-16 18:44 ` xry111 at gcc dot gnu.org
2023-12-16 20:11 ` [Bug middle-end/113033] " xry111 at gcc dot gnu.org
2023-12-16 21:35 ` xry111 at gcc dot gnu.org [this message]
2023-12-18 13:47 ` xry111 at gcc dot gnu.org
2023-12-18 20:17 ` [Bug target/113033] " xry111 at gcc dot gnu.org
2023-12-18 20:34 ` xry111 at gcc dot gnu.org
2023-12-20 12:02 ` cvs-commit at gcc dot gnu.org
2023-12-20 12:05 ` xry111 at gcc dot gnu.org
2023-12-27 11:05 ` 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-113033-4-Vl5iZDP2fD@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).