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 middle-end/113179] [11/12/13/14 Regression] MIPS: INS is used for long long, before SLL Date: Sun, 31 Dec 2023 06:44:21 +0000 [thread overview] Message-ID: <bug-113179-4-GQGUWFB4Ly@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 ---------------------------------------------------------------------------- Component|rtl-optimization |middle-end Ever confirmed|0 |1 Keywords| |needs-bisection Last reconfirmed| |2023-12-31 Status|UNCONFIRMED |NEW --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- 5.4 produced during expand: ``` (insn 10 7 11 2 (set (reg:QI 198 [ D.1502 ]) (truncate:QI (reg/v:DI 197 [ b ]))) /app/example.cpp:10 -1 (nil)) (insn 11 10 12 2 (set (reg:SI 199) (mem/j:SI (reg/v/f:DI 196 [ a ]) [1 a_5(D)->d+-3 S4 A32])) /app/example.cpp:10 -1 (nil)) (insn 12 11 13 2 (set (zero_extract:SI (reg:SI 199) (const_int 1 [0x1]) (const_int 0 [0])) (subreg:SI (reg:QI 198 [ D.1502 ]) 0)) /app/example.cpp:10 -1 (nil)) ``` But 11.2.0 produces: ``` (insn 10 7 11 2 (set (reg:SI 197) (mem/j:SI (reg/v/f:DI 195 [ a ]) [1 a_4(D)->d+-3 S4 A32])) "/app/example.cpp":10:14 -1 (nil)) (insn 11 10 12 2 (set (zero_extract:SI (reg:SI 197) (const_int 1 [0x1]) (const_int 0 [0])) (subreg:SI (reg/v:DI 196 [ b ]) 4)) "/app/example.cpp":10:14 -1 (nil)) ``` The truncate is missing ... Would be interesting to do a bisect here on what caused the wrong code ...
next prev parent reply other threads:[~2023-12-31 6:44 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 ` [Bug rtl-optimization/113179] [11/12/13/14 Regression] MIPS: INS is used for long long, before SLL pinskia at gcc dot gnu.org 2023-12-31 6:44 ` pinskia at gcc dot gnu.org [this message] 2024-03-04 4:20 ` [Bug middle-end/113179] " 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-GQGUWFB4Ly@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).