public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/97502] [11 Regression] PGO bootstrap failure on s390x-linux with -march=z13 starting with r11-3426 Date: Tue, 20 Oct 2020 14:13:18 +0000 [thread overview] Message-ID: <bug-97502-4-Rb4Hjd5LAU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97502-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97502 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- With --- gcc/config/s390/vx-builtins.md.jj 2020-04-30 09:26:01.000000000 +0200 +++ gcc/config/s390/vx-builtins.md 2020-10-20 16:08:31.847698827 +0200 @@ -812,6 +812,16 @@ DONE; }) +(define_expand "vec_cmp<intcmp:code><VI_HW:mode><VI_HW:mode>" + [(set (match_operand:VI_HW 0 "register_operand" "=v") + (intcmp:VI_HW (match_operand:VI_HW 1 "register_operand" "v") + (match_operand:VI_HW 2 "register_operand" "v")))] + "TARGET_VX" +{ + s390_expand_vec_compare (operands[0], <intcmp:CODE>, operands[1], operands[2]); + DONE; +}) + (define_expand "vec_cmp<fpcmp:code><mode>" [(set (match_operand:<tointvec> 0 "register_operand" "=v") (fpcmp:<tointvec> (match_operand:VF_HW 1 "register_operand" "v") (couldn't just change the existing pattern easily as s390.c refers to the current names) the testcase doesn't ICE anymore, but whether it does the right thing is unclear. Anyway, deferring to s390x maintainers now.
next prev parent reply other threads:[~2020-10-20 14:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-20 13:08 [Bug bootstrap/97502] New: " jakub at gcc dot gnu.org 2020-10-20 13:08 ` [Bug bootstrap/97502] " jakub at gcc dot gnu.org 2020-10-20 13:14 ` marxin at gcc dot gnu.org 2020-10-20 13:53 ` rguenth at gcc dot gnu.org 2020-10-20 14:00 ` rguenth at gcc dot gnu.org 2020-10-20 14:04 ` rguenth at gcc dot gnu.org 2020-10-20 14:05 ` jakub at gcc dot gnu.org 2020-10-20 14:13 ` jakub at gcc dot gnu.org [this message] 2020-10-21 5:55 ` krebbel at gcc dot gnu.org 2020-10-22 10:39 ` cvs-commit at gcc dot gnu.org 2020-10-22 10:49 ` 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-97502-4-Rb4Hjd5LAU@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).