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: Thu, 23 Jun 2022 23:18:36 +0000 [thread overview]
Message-ID: <bug-106069-4-OcL0iwUw9u@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 #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
The difference between r12-4495 and r12-4496:
$ diff -up b/q.C.252r.expand a/q.C.252r.expand
--- b/q.C.252r.expand 2022-06-23 23:16:44.753507476 +0000
+++ a/q.C.252r.expand 2022-06-23 23:16:16.232784087 +0000
@@ -831,10 +831,14 @@ try_optimize_cfg iteration 2
(subreg:V16QI (reg/v:V4SI 168 [ R02$m_simd ]) 0)) "q.C":31:47 -1
(nil))
(insn 188 187 189 5 (set (reg:V4SI 339)
- (unspec:V4SI [
- (subreg:V4SI (reg:V16QI 338) 0)
- (subreg:V4SI (reg:V16QI 337) 0)
- ] UNSPEC_VMRGL_DIRECT)) "q.C":31:47 -1
+ (vec_select:V4SI (vec_concat:V8SI (subreg:V4SI (reg:V16QI 338) 0)
+ (subreg:V4SI (reg:V16QI 337) 0))
+ (parallel [
+ (const_int 2 [0x2])
+ (const_int 6 [0x6])
+ (const_int 3 [0x3])
+ (const_int 7 [0x7])
+ ]))) "q.C":31:47 -1
(nil))
(insn 189 188 190 5 (set (reg:V16QI 336)
(subreg:V16QI (reg:V4SI 339) 0)) "q.C":31:47 -1
@@ -846,10 +850,14 @@ try_optimize_cfg iteration 2
(subreg:V16QI (reg/v:V4SI 143 [ val ]) 0)) "q.C":32:47 -1
(nil))
(insn 192 191 193 5 (set (reg:V4SI 344)
- (unspec:V4SI [
- (subreg:V4SI (reg:V16QI 343) 0)
- (subreg:V4SI (reg:V16QI 342) 0)
- ] UNSPEC_VMRGL_DIRECT)) "q.C":32:47 -1
+ (vec_select:V4SI (vec_concat:V8SI (subreg:V4SI (reg:V16QI 343) 0)
+ (subreg:V4SI (reg:V16QI 342) 0))
+ (parallel [
+ (const_int 2 [0x2])
+ (const_int 6 [0x6])
+ (const_int 3 [0x3])
+ (const_int 7 [0x7])
+ ]))) "q.C":32:47 -1
(nil))
(insn 193 192 194 5 (set (reg:V16QI 341)
(subreg:V16QI (reg:V4SI 344) 0)) "q.C":32:47 -1
@@ -861,10 +869,14 @@ try_optimize_cfg iteration 2
(subreg:V4SI (reg:V16QI 341) 0)) "q.C":35:8 -1
(nil))
(insn 196 195 197 5 (set (reg:V4SI 349)
- (unspec:V4SI [
- (subreg:V4SI (reg:V16QI 341) 0)
- (subreg:V4SI (reg:V16QI 336) 0)
- ] UNSPEC_VMRGL_DIRECT)) "q.C":35:8 -1
+ (vec_select:V4SI (vec_concat:V8SI (subreg:V4SI (reg:V16QI 341) 0)
+ (subreg:V4SI (reg:V16QI 336) 0))
+ (parallel [
+ (const_int 2 [0x2])
+ (const_int 6 [0x6])
+ (const_int 3 [0x3])
+ (const_int 7 [0x7])
+ ]))) "q.C":35:8 -1
(nil))
(insn 197 196 198 5 (set (reg:V16QI 348)
(subreg:V16QI (reg:V4SI 349) 0)) "q.C":35:8 -1
@@ -934,7 +946,7 @@ try_optimize_cfg iteration 2
(reg/f:DI 120)) "q.C":103:7 -1
(nil))
(call_insn 9 8 10 2 (parallel [
- (call (mem:SI (symbol_ref:DI ("_Z3fooPhPj") [flags 0x3]
<function_decl 0x3fff7f473a00 foo>) [0 foo S4 A8])
+ (call (mem:SI (symbol_ref:DI ("_Z3fooPhPj") [flags 0x3]
<function_decl 0x3fffa9823a00 foo>) [0 foo S4 A8])
(const_int 0 [0]))
(use (const_int 0 [0]))
(clobber (reg:DI 96 lr))
@@ -968,7 +980,7 @@ try_optimize_cfg iteration 2
-> 17)
(note 14 13 15 4 [bb 4] NOTE_INSN_BASIC_BLOCK)
(call_insn 15 14 16 4 (parallel [
- (call (mem:SI (symbol_ref:DI ("abort") [flags 0x41]
<function_decl 0x3fff7f2b5300 __builtin_abort>) [0 __builtin_abort S4 A8])
+ (call (mem:SI (symbol_ref:DI ("abort") [flags 0x41]
<function_decl 0x3fffa9665300 __builtin_abort>) [0 __builtin_abort S4 A8])
(const_int 0 [0]))
(use (const_int 0 [0]))
(clobber (reg:DI 96 lr))
next prev parent reply other threads:[~2022-06-23 23:18 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 [this message]
2022-06-24 3:25 ` luoxhu at gcc dot gnu.org
2022-06-24 13:03 ` mpolacek at gcc dot gnu.org
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-OcL0iwUw9u@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).