From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: New AArch64 GAS testsuite failure for CSSC
Date: Tue, 15 Nov 2022 14:46:27 +0000 [thread overview]
Message-ID: <2ffd3e5e-7436-d06a-6d97-30225a79902e@arm.com> (raw)
In-Reply-To: <95438b50-e46e-d9f6-712e-b4a5323a09f7@arm.com>
Nope... can't reproduce on aarch64_be-linux-gnu either. Could you check
again? How exactly are you configuring your toolchain? I used 'configure
--disable-sim --disable-gdb --target=aarch64_be-linux-gnu' and was built
in an aarch64-linux-gnu host.
Kind regards,
Andre
On 15/11/2022 14:43, Andre Vieira (lists) via Binutils wrote:
> Hi Nick,
>
> I committed attached patch as obvious to fix the first issue and I was
> about to say I couldn't reproduce the big endian failure, but I just
> noticed I was building a aarch64_be-none-elf. I'll go have a look at
> aarch64_be-linux-gnu now...
>
> Kind regards,
> Andre
>
> On 15/11/2022 10:42, Nick Clifton wrote:
>> Hi Andre,
>>
>> I am seeing a new testsuite failure in the GAS testsuite for AArch64
>> targets. There appear to be two problems. For a toolchain configured
>> as aarch64-linux-gnu it seems that the regexps do not match. (There
>> appears to be some extra text in gas/testsuite/gas/aarch64/cssc.d that
>> is not present in the disassembler output).
>>
>> Secondly, for a toolchain configured as aarch64_be-linux-gnu the test
>> source file does not assemble at all. :-(
>>
>> Please could you fix these problems ?
>>
>> Cheers
>> Nick
>>
next prev parent reply other threads:[~2022-11-15 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 10:42 Nick Clifton
2022-11-15 14:04 ` Andre Vieira (lists)
2022-11-15 14:43 ` Andre Vieira (lists)
2022-11-15 14:46 ` Andre Vieira (lists) [this message]
2022-11-15 15:09 ` Nick Clifton
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=2ffd3e5e-7436-d06a-6d97-30225a79902e@arm.com \
--to=andre.simoesdiasvieira@arm.com \
--cc=binutils@sourceware.org \
--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).