public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106069] [12/13 Regression] wrong code with -O -fno-tree-forwprop -maltivec on ppc64le
Date: Fri, 24 Jun 2022 13:03:04 +0000 [thread overview]
Message-ID: <bug-106069-4-32FoookK2r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106069-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Sure. (If you're looking for a ppc64le machine, the compile farm has a few.)
$ diff -up q95.s q96.s
--- q95.s 2022-06-23 23:08:22.870777519 +0000
+++ q96.s 2022-06-23 23:08:10.990476157 +0000
@@ -12,12 +12,12 @@ _Z3fooPhPj:
0: addis 2,12,.TOC.-.LCF0@ha
addi 2,2,.TOC.-.LCF0@l
.localentry _Z3fooPhPj,.-_Z3fooPhPj
- lxsiwzx 50,0,4
+ lxsiwzx 49,0,4
xxlxor 0,0,0
- xxpermdi 50,0,50,0
+ xxpermdi 49,0,49,0
addi 9,4,8
- lxsiwzx 51,0,9
- xxpermdi 51,0,51,0
+ lxsiwzx 50,0,9
+ xxpermdi 50,0,50,0
addi 9,4,20
lxsiwzx 44,0,9
xxpermdi 44,0,44,0
@@ -28,8 +28,8 @@ _Z3fooPhPj:
lxsiwzx 32,0,9
xxpermdi 32,0,32,0
addi 9,4,32
- lxsiwzx 49,0,9
- xxpermdi 49,0,49,0
+ lxsiwzx 34,0,9
+ xxpermdi 34,0,34,0
addi 9,4,36
lxsiwzx 43,0,9
xxpermdi 43,0,43,0
@@ -40,8 +40,8 @@ _Z3fooPhPj:
lxsiwzx 33,0,9
xxpermdi 33,0,33,0
addi 9,4,48
- lxsiwzx 34,0,9
- xxpermdi 34,0,34,0
+ lxsiwzx 35,0,9
+ xxpermdi 35,0,35,0
addi 9,4,52
lxsiwzx 38,0,9
xxpermdi 38,0,38,0
@@ -51,14 +51,14 @@ _Z3fooPhPj:
addi 9,4,60
lxsiwzx 39,0,9
xxpermdi 39,0,39,0
- xxlor 48,50,50
- xxlor 35,50,50
+ xxlor 47,49,49
+ xxlor 51,49,49
addis 9,2,.LC0@toc@ha
addi 9,9,.LC0@toc@l
lvx 4,0,9
addis 9,2,.LC1@toc@ha
addi 9,9,.LC1@toc@l
- lvx 15,0,9
+ lvx 16,0,9
li 9,10
mtctr 9
.L2:
@@ -68,34 +68,30 @@ _Z3fooPhPj:
xxlxor 45,45,37
xxlxor 32,32,33
vrlw 0,0,4
- vadduwm 8,3,12
- vadduwm 9,16,13
- vadduwm 10,19,0
- vadduwm 3,8,12
- vadduwm 16,9,13
- vadduwm 19,10,0
- xxlxor 40,40,35
+ vadduwm 8,19,12
+ vadduwm 9,15,13
+ vadduwm 10,18,0
+ vadduwm 19,8,12
+ vadduwm 15,9,13
+ vadduwm 18,10,0
+ xxlxor 40,40,51
xxlxor 39,39,40
- xxlxor 41,34,41
- vrlw 2,9,15
+ xxlxor 41,35,41
+ vrlw 3,9,16
xxlxor 42,38,42
- vrlw 6,10,15
+ vrlw 6,10,16
vadduwm 5,5,7
- vadduwm 1,1,2
- vadduwm 17,17,6
+ vadduwm 1,1,3
+ vadduwm 2,2,6
vadduwm 11,11,14
xxlxor 44,37,44
vrlw 12,12,4
xxlxor 45,33,45
vrlw 13,13,4
- xxlxor 32,49,32
+ xxlxor 32,34,32
vrlw 0,0,4
bdnz .L2
- vadduwm 3,3,18
- xxmrglw 51,51,35
- xxmrglw 50,50,48
- xxmrglw 50,50,51
- vspltw 0,18,3
+ vspltw 0,17,0
mfvsrwz 9,32
stb 9,0(3)
blr
next prev parent reply other threads:[~2022-06-24 13:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 23:13 [Bug target/106069] New: " mpolacek at gcc dot gnu.org
2022-06-23 23:15 ` [Bug target/106069] [12/13 Regression] " mpolacek at gcc dot gnu.org
2022-06-23 23:18 ` mpolacek at gcc dot gnu.org
2022-06-24 3:25 ` luoxhu at gcc dot gnu.org
2022-06-24 13:03 ` mpolacek at gcc dot gnu.org [this message]
2022-06-30 8:13 ` luoxhu at gcc dot gnu.org
2022-06-30 8:15 ` luoxhu at gcc dot gnu.org
2022-06-30 17:32 ` segher at gcc dot gnu.org
2022-06-30 17:34 ` segher at gcc dot gnu.org
2022-07-01 1:52 ` luoxhu at gcc dot gnu.org
2022-07-25 15:54 ` rguenth at gcc dot gnu.org
2022-07-25 20:16 ` segher at gcc dot gnu.org
2022-07-25 20:18 ` segher at gcc dot gnu.org
2022-07-26 3:34 ` luoxhu at gcc dot gnu.org
2022-07-26 3:34 ` luoxhu at gcc dot gnu.org
2022-07-26 3:35 ` luoxhu at gcc dot gnu.org
2022-07-26 3:53 ` luoxhu at gcc dot gnu.org
2022-07-26 6:28 ` luoxhu at gcc dot gnu.org
2022-07-29 11:10 ` rguenth at gcc dot gnu.org
2022-07-29 11:21 ` rguenth at gcc dot gnu.org
2022-08-03 6:10 ` yinyuefengyi at gmail dot com
2022-08-03 6:38 ` yinyuefengyi at gmail dot com
2022-08-03 8:06 ` linkw at gcc dot gnu.org
2022-08-03 8:24 ` rguenther at suse dot de
2022-08-03 8:50 ` linkw at gcc dot gnu.org
2022-08-03 8:59 ` rguenth at gcc dot gnu.org
2022-08-03 9:20 ` rsandifo at gcc dot gnu.org
2022-08-03 9:25 ` rsandifo at gcc dot gnu.org
2022-08-03 18:01 ` segher at gcc dot gnu.org
2022-08-03 18:06 ` segher at gcc dot gnu.org
2022-08-04 9:17 ` rsandifo at gcc dot gnu.org
2022-08-04 9:21 ` rearnsha at gcc dot gnu.org
2022-08-04 9:59 ` yinyuefengyi at gmail dot com
2022-08-04 10:01 ` yinyuefengyi at gmail dot com
2023-01-16 18:00 ` jakub at gcc dot gnu.org
2023-03-24 16:16 ` jakub at gcc dot gnu.org
2023-03-24 17:01 ` bergner at gcc dot gnu.org
2023-03-31 2:57 ` yinyuefengyi at gmail dot com
2023-05-08 12:24 ` [Bug target/106069] [12/13/14 " rguenth 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-106069-4-32FoookK2r@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).