public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/100328] IRA doesn't model matching constraint well Date: Mon, 28 Jun 2021 05:25:25 +0000 [thread overview] Message-ID: <bug-100328-4-YZpkMgu0jS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100328-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100328 --- Comment #6 from Kewen Lin <linkw at gcc dot gnu.org> --- Created attachment 51066 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51066&action=edit aarch64 XPASS failure list The patch v3 bootstrapped and regression-tested on x86_64-redhat-linux and powerpc64le-linux-gnu, but still have some "XFAIL -> XPASS" regression failures on aarch64-linux-gnu, I think these remaining failures are expected (assembly gets improved). Need Richard's help to double check/confirm them. For example, for div_f16.c, mad_f32.c and sub_f64.c, the related different assembly looks like below: BEFORE: div_h4_f16_x_untied: mov z4.h, h4 movprfx z0, z1 fdiv z0.h, p0/m, z0.h, z4.h ret mad_s4_f32_x_untied: mov z4.s, s4 movprfx z0, z4 fmla z0.s, p0/m, z1.s, z2.s ret sub_d4_f64_x_untied: mov z4.d, d4 movprfx z0, z1 fsub z0.d, p0/m, z0.d, z4.d ret AFTER: div_h4_f16_x_untied: mov z0.h, h4 fdivr z0.h, p0/m, z0.h, z1.h ret mad_s4_f32_x_untied: mov z0.s, s4 fmla z0.s, p0/m, z1.s, z2.s ret sub_d4_f64_x_untied: mov z0.d, d4 fsubr z0.d, p0/m, z0.d, z1.d ret The assembly with this patch saves movprfx.
next prev parent reply other threads:[~2021-06-28 5:25 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-29 6:41 [Bug rtl-optimization/100328] New: IRA doesn't model dup num " linkw at gcc dot gnu.org 2021-04-30 8:30 ` [Bug rtl-optimization/100328] " linkw at gcc dot gnu.org 2021-06-23 18:28 ` [Bug rtl-optimization/100328] IRA doesn't model matching " vmakarov at gcc dot gnu.org 2021-06-24 12:11 ` linkw at gcc dot gnu.org 2021-06-24 12:36 ` linkw at gcc dot gnu.org 2021-06-28 3:27 ` linkw at gcc dot gnu.org 2021-06-28 5:25 ` linkw at gcc dot gnu.org [this message] 2021-06-29 16:01 ` rsandifo at gcc dot gnu.org 2021-07-01 6:18 ` linkw at gcc dot gnu.org 2021-07-06 2:35 ` cvs-commit at gcc dot gnu.org 2021-07-06 2:35 ` cvs-commit at gcc dot gnu.org 2021-07-07 3:07 ` linkw 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-100328-4-YZpkMgu0jS@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).