From: YunQiang Su <wzssyqa@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
gcc-patches@gcc.gnu.org, jlaw@ventanamicro.com,
rdapp.gcc@gmail.com, richard.sandiford@arm.com
Subject: Re: [PATCH] Add a late-combine pass [PR106594]
Date: Wed, 26 Jun 2024 01:22:03 +0800 [thread overview]
Message-ID: <CAKcpw6VFXNvxJ6OpxUJRezztc2fcgeMjSMNtBPpzk_hu0r3dWw@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc34spn5TvyULUzmcbLg1CT6MhxAf_zO0t3R55zU2X=cQg@mail.gmail.com>
Just FYI. This patch does something to gcc.target/mips/madd-8.c, and
gcc.target/mips/msub-8.c.
-PASS: gcc.target/mips/madd-8.c -O2 scan-assembler \tmul\t
-PASS: gcc.target/mips/madd-8.c -O2 scan-assembler-not \tmadd\t
-PASS: gcc.target/mips/madd-8.c -O2 scan-assembler-not \tmflo\t
-PASS: gcc.target/mips/madd-8.c -O2 scan-assembler-not \tmtlo\t
+FAIL: gcc.target/mips/madd-8.c -O2 scan-assembler \tmul\t
+FAIL: gcc.target/mips/madd-8.c -O2 scan-assembler-not \tmadd\t
+FAIL: gcc.target/mips/madd-8.c -O2 scan-assembler-not \tmflo\t
+FAIL: gcc.target/mips/madd-8.c -O2 scan-assembler-not \tmtlo\t
-FAIL: gcc.target/mips/msub-8.c -O2 scan-assembler \tmul\t
-FAIL: gcc.target/mips/msub-8.c -O2 scan-assembler-not \tmflo\t
-FAIL: gcc.target/mips/msub-8.c -O2 scan-assembler-not \tmsub\t
-FAIL: gcc.target/mips/msub-8.c -O2 scan-assembler-not \tmtlo\t
+PASS: gcc.target/mips/msub-8.c -O2 scan-assembler \tmul\t
+PASS: gcc.target/mips/msub-8.c -O2 scan-assembler-not \tmflo\t
+PASS: gcc.target/mips/msub-8.c -O2 scan-assembler-not \tmsub\t
+PASS: gcc.target/mips/msub-8.c -O2 scan-assembler-not \tmtlo\t
Quite interesting. I will inverest the real reason.
next prev parent reply other threads:[~2024-06-25 17:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 18:49 Richard Sandiford
2023-11-30 14:10 ` Ping: " Richard Sandiford
2023-12-11 15:23 ` Richard Sandiford
2023-12-11 16:18 ` Robin Dapp
2023-12-30 15:35 ` Ping^3: " Richard Sandiford
2024-01-01 3:11 ` YunQiang Su
2024-01-05 10:10 ` YunQiang Su
2023-12-30 18:13 ` Segher Boessenkool
2024-01-02 9:47 ` Richard Sandiford
2024-06-24 19:37 ` Segher Boessenkool
2024-06-25 10:31 ` Richard Biener
2024-06-25 17:22 ` YunQiang Su [this message]
2024-01-03 4:20 ` Jeff Law
2024-01-05 17:35 ` Richard Sandiford
2024-01-08 5:03 ` Jeff Law
2024-01-08 11:52 ` Richard Sandiford
2024-01-08 16:14 ` Jeff Law
2024-01-08 16:59 ` Richard Sandiford
2024-01-08 17:10 ` Jeff Law
2024-01-08 19:11 ` Richard Sandiford
2024-01-08 21:42 ` Jeff Law
2024-01-10 13:01 ` Richard Sandiford
2024-01-10 13:35 ` Richard Biener
2024-01-10 16:27 ` Jeff Law
2024-01-10 16:40 ` Jeff Law
2024-06-21 4:50 ` Hongtao Liu
2024-06-27 16:49 ` nvptx vs. " Thomas Schwinge
2024-06-27 20:27 ` Thomas Schwinge
2024-06-27 21:20 ` Thomas Schwinge
2024-06-27 22:41 ` Thomas Schwinge
2024-06-28 14:01 ` Richard Sandiford
2024-06-28 16:48 ` Richard Sandiford
2024-07-01 11:55 ` Thomas Schwinge
2024-07-01 11:55 ` WIP Move 'pass_fast_rtl_dce' from 'pass_postreload' into 'pass_late_compilation' (was: nvptx vs. [PATCH] Add a late-combine pass [PR106594]) Thomas Schwinge
2024-06-28 6:07 ` nvptx vs. [PATCH] Add a late-combine pass [PR106594] Roger Sayle
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=CAKcpw6VFXNvxJ6OpxUJRezztc2fcgeMjSMNtBPpzk_hu0r3dWw@mail.gmail.com \
--to=wzssyqa@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=rdapp.gcc@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=segher@kernel.crashing.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).