From: Segher Boessenkool <segher@kernel.crashing.org>
To: Aaron Sawdey <acsawdey@linux.ibm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH,rs6000] Fix p10 fusion test cases for -m32
Date: Wed, 9 Jun 2021 09:38:18 -0500 [thread overview]
Message-ID: <20210609143818.GE18427@gate.crashing.org> (raw)
In-Reply-To: <4320298D-2A9E-4FEC-BD26-25D695CD6AE7@linux.ibm.com>
On Wed, May 26, 2021 at 04:53:24PM -0500, Aaron Sawdey wrote:
> > The counts of fusion insns are slightly different for 32-bit compiles
> > so we need different scan-assembler-times counts for 32 and 64 bit
> > in the test cases for p10 fusion.
Have you checked all of these actually make sense? It seems too be
two themes: long long being two regs / two insns on 32-bit, and the
you get cmpld etc. only on 64-bit?
Okay for trunk if this is actually the expected output. Thanks!
Segher
prev parent reply other threads:[~2021-06-09 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1621968336-99949-1-git-send-email-acsawdey@linux.ibm.com>
2021-05-26 21:53 ` Aaron Sawdey
2021-06-09 14:38 ` Segher Boessenkool [this message]
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=20210609143818.GE18427@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=acsawdey@linux.ibm.com \
--cc=gcc-patches@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).