public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112103] [14 regression] gcc.target/powerpc/rlwinm-0.c fails after r14-4941-gd1bb9569d70304
Date: Thu, 09 Nov 2023 18:35:08 +0000 [thread overview]
Message-ID: <bug-112103-4-MIs1M7gd9g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112103-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112103
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Those are:
$ diff -up rlwinm-0.s{.12,}
--- rlwinm-0.s.12 2023-11-09 18:28:49.362639203 +0000
+++ rlwinm-0.s 2023-11-09 18:30:46.422896735 +0000
@@ -6747,7 +6747,7 @@ f_1_16_31:
.LFB345:
.cfi_startproc
rlwinm 3,3,1,16,31
- rlwinm 3,3,0,0xffff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -7645,7 +7645,7 @@ f_1_24_31:
.LFB390:
.cfi_startproc
rlwinm 3,3,1,24,31
- rlwinm 3,3,0,0xff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -11235,7 +11235,7 @@ f_2_16_31:
.LFB570:
.cfi_startproc
rlwinm 3,3,2,16,31
- rlwinm 3,3,0,0xffff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -12133,7 +12133,7 @@ f_2_24_31:
.LFB615:
.cfi_startproc
rlwinm 3,3,2,24,31
- rlwinm 3,3,0,0xff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -15722,7 +15722,7 @@ f_7_16_31:
.LFB795:
.cfi_startproc
rlwinm 3,3,7,16,31
- rlwinm 3,3,0,0xffff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -16620,7 +16620,7 @@ f_7_24_31:
.LFB840:
.cfi_startproc
rlwinm 3,3,7,24,31
- rlwinm 3,3,0,0xff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -20207,7 +20207,7 @@ f_8_16_31:
.LFB1020:
.cfi_startproc
rlwinm 3,3,8,16,31
- rlwinm 3,3,0,0xffff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -24691,7 +24691,7 @@ f_9_16_31:
.LFB1245:
.cfi_startproc
rlwinm 3,3,9,16,31
- rlwinm 3,3,0,0xffff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -29174,7 +29174,7 @@ f_15_16_31:
.LFB1470:
.cfi_startproc
rlwinm 3,3,15,16,31
- rlwinm 3,3,0,0xffff
+ rldicl 3,3,0,32
blr
.long 0
.byte 0,0,0,0,0,0,0,0
@@ -67092,4 +67092,4 @@ f_31_31_31:
.cfi_endproc
.LFE3375:
.size f_31_31_31,.-.L.f_31_31_31
- .ident "GCC: (GNU) 12.0.1 20220406 (experimental)"
+ .ident "GCC: (GNU) 14.0.0 20231103 (experimental)"
next prev parent reply other threads:[~2023-11-09 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 16:44 [Bug target/112103] New: " seurer at gcc dot gnu.org
2023-10-26 21:34 ` [Bug target/112103] " roger at nextmovesoftware dot com
2023-10-27 13:03 ` rguenth at gcc dot gnu.org
2023-11-09 18:35 ` segher at gcc dot gnu.org [this message]
2023-11-09 18:37 ` segher at gcc dot gnu.org
2024-01-15 13:57 ` rguenth at gcc dot gnu.org
2024-01-19 16:48 ` bergner at gcc dot gnu.org
2024-02-16 19:01 ` jakub at gcc dot gnu.org
2024-02-19 21:42 ` bergner at gcc dot gnu.org
2024-02-19 22:24 ` bergner at gcc dot gnu.org
2024-02-19 22:40 ` bergner at gcc dot gnu.org
2024-02-20 19:45 ` cvs-commit at gcc dot gnu.org
2024-02-20 19:52 ` bergner 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-112103-4-MIs1M7gd9g@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).