From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: "hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"Gopalasubramanian, Ganesh" <Ganesh.Gopalasubramanian@amd.com>,
"Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>
Subject: Re: [PATCH] Add AMD znver5 processor support
Date: Fri, 5 Jan 2024 12:11:21 +0100 [thread overview]
Message-ID: <b7a303bc-40d8-4317-89fc-a11907997cdb@suse.com> (raw)
In-Reply-To: <4dbbaa61-8e86-4b4a-8bc4-65d88a005d03@redhat.com>
On 05.01.2024 10:35, Nick Clifton wrote:
> Hi Jan, Hi Joshi,
>
> Two new failures in the gas testsuite for PE based x86_64
> toolchains has just appeared:
>
> FAIL: x86-64 arch 5
> FAIL: x86-64 arch 5 (znver5)
>
> It looks like a simple regexp problem:
>
> regexp_diff match failure
> regexp "^[ ]*[a-f0-9]+:[ ]*0f 18 3d 78 56 34 12[ ]*prefetchit0 0x12345678\(%rip\) # 0x[0-9a-f]+$"
> line " 15: 0f 18 3d 78 56 34 12 prefetchit0 0x12345678(%rip) # 12345694 <.text+0x12345694>"
>
> Could you take a look please ?
Correction pushed. I'm puzzled though that this test isn't run when
building a 64-bit capable assembler for 32-bit Cygwin (I first meant
to reply: Cannot reproduce), despite --help output mentioning the
necessary --64 command line option. That looks to be something in
need of (further) improvement.
Jan
prev parent reply other threads:[~2024-01-05 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 7:12 Joshi, Tejas Sanjay
2023-12-22 11:15 ` Jan Beulich
2023-12-26 3:29 ` Joshi, Tejas Sanjay
2024-01-04 8:19 ` Jan Beulich
2024-01-04 9:30 ` Joshi, Tejas Sanjay
2024-01-05 8:29 ` Jan Beulich
2024-01-05 9:35 ` Nick Clifton
2024-01-05 11:11 ` Jan Beulich [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=b7a303bc-40d8-4317-89fc-a11907997cdb@suse.com \
--to=jbeulich@suse.com \
--cc=Ganesh.Gopalasubramanian@amd.com \
--cc=TejasSanjay.Joshi@amd.com \
--cc=Venkataramanan.Kumar@amd.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=nickc@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).