public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/113179] [11/12/13/14 Regression] MIPS: INS is used for long long, before SLL
Date: Sun, 31 Dec 2023 06:42:13 +0000 [thread overview]
Message-ID: <bug-113179-4-fZ97dGj1BR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113179-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113179
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |11.5
Target| |mips64-linux-gnu
Summary|MIPS: INS is used for long |[11/12/13/14 Regression]
|long, before SLL |MIPS: INS is used for long
| |long, before SLL
Known to work| |5.4.0
Known to fail| |11.2.0
Component|target |rtl-optimization
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed, this is a regression. I think it used to work in GCC 7.3.0 also (but
I have around is modified octeon compiler).
next prev parent reply other threads:[~2023-12-31 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 10:36 [Bug target/113179] New: MIPS syq at gcc dot gnu.org
2023-12-31 6:42 ` pinskia at gcc dot gnu.org [this message]
2023-12-31 6:44 ` [Bug middle-end/113179] [11/12/13/14 Regression] MIPS: INS is used for long long, before SLL pinskia at gcc dot gnu.org
2024-03-04 4:20 ` law at gcc dot gnu.org
2024-04-27 9:16 ` [Bug middle-end/113179] [11/12/13/14/15 " syq at gcc dot gnu.org
2024-05-06 4:10 ` cvs-commit at gcc dot gnu.org
2024-05-06 4:13 ` syq at gcc dot gnu.org
2024-05-06 4:15 ` syq at gcc dot gnu.org
2024-05-06 4:18 ` 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-113179-4-fZ97dGj1BR@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).