public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Surya Kumari Jangala <jskumari@linux.vnet.ibm.com>
To: Richard Sandiford <richard.sandiford@arm.com>,
	Peter Bergner <bergner@linux.ibm.com>
Cc: GCC Development <gcc@gcc.gnu.org>, vmakarov@redhat.com
Subject: Discussion about arm testcase failures seen with patch for PR111673
Date: Fri, 3 Nov 2023 16:58:40 +0530	[thread overview]
Message-ID: <51f4b26f-1462-45c2-8106-fbfe8dc61975@linux.vnet.ibm.com> (raw)

Hi Richard,
I had submitted a patch for review (https://gcc.gnu.org/pipermail/gcc-patches/2023-October/631849.html)
regarding scaling save/restore costs of callee save registers with block
frequency in the IRA pass (PR111673).

This patch has been approved by VMakarov 
(https://gcc.gnu.org/pipermail/gcc-patches/2023-October/632089.html).

With this patch, we are seeing performance improvements with spec on x86 
(exchange: 5%, xalancbmk: 2.5%) and on Power (perlbench: 5.57%).

I received a mail from Linaro about some failures seen in the CI pipeline with
this patch. I have analyzed the failures and I wish to discuss the analysis with you.

One failure reported by the Linaro CI is:

FAIL: gcc.target/arm/pr111235.c scan-assembler-times ldrexd\tr[0-9]+, r[0-9]+, \\[r[0-9]+\\] 2

The diff in the assembly between trunk and patch is:

93c93
<       push    {r4, r5}
---
>       push    {fp}
95c95
<       ldrexd  r4, r5, [r0]
---
>       ldrexd  fp, ip, [r0]
99c99
<       pop     {r4, r5}
---
>       ldr     fp, [sp], #4


The test fails with patch because the ldrexd insn uses fp & ip registers instead
of r[0-9]+

But the code produced by patch is better because it is pushing and restoring only
one register (fp) instead of two registers (r4, r5). Hence, this test can be
modified to allow it to pass on arm. Please let me know what you think.

If you need more information, please let me know. I will be sending separate mails
for the other test failures.

Regards,
Surya




             reply	other threads:[~2023-11-03 11:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 11:28 Surya Kumari Jangala [this message]
2023-11-24  8:09 ` Surya Kumari Jangala
2023-11-24 10:48   ` Richard Earnshaw
2023-11-28 12:52     ` Discussion about arm/aarch64 " Surya Kumari Jangala
2023-11-28 13:48       ` Richard Earnshaw
2023-11-28 15:41         ` Richard Sandiford
2023-12-14  7:17         ` Surya Kumari Jangala
2023-12-14 16:11           ` Richard Earnshaw (lists)
2023-12-15 17:04             ` Surya Kumari Jangala
2024-01-29  6:14               ` Surya Kumari Jangala

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=51f4b26f-1462-45c2-8106-fbfe8dc61975@linux.vnet.ibm.com \
    --to=jskumari@linux.vnet.ibm.com \
    --cc=bergner@linux.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.sandiford@arm.com \
    --cc=vmakarov@redhat.com \
    /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).