From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Taylor Simpson" <tsimpson@quicinc.com>
Cc: "fam@euphon.net" <fam@euphon.net>,
"berrange@redhat.com" <berrange@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"f4bug@amsat.org" <f4bug@amsat.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"crosa@redhat.com" <crosa@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"aurelien@aurel32.net" <aurelien@aurel32.net>
Subject: Re: [RFC PATCH 0/4] improve coverage of vector backend
Date: Fri, 4 Feb 2022 08:31:38 +1100 [thread overview]
Message-ID: <b5cfbd97-8f10-c41f-d28d-bf2567585e99@linaro.org> (raw)
In-Reply-To: <87h79fsor3.fsf@linaro.org>
On 2/4/22 07:00, Alex Bennée wrote:
>>> Does:
>>>
>>> #if BYTE_ORDER == BIG_ENDIAN
>>>
>>> work for your compiler?
>>
>> No, but this does
>> #if __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
>>
>> With that change in the source, the tests passes. Will that work for
>> other targets?
>
> At least not hppa-linux-user. The joy of having no standard compile time
> way to report byte order in the C standard despite most things needing
> to know one way or another.
>
> Richard,
>
> Any ideas?
I see you're not explicitly including <endian.h>.
I would expect that to be of some use.
r~
prev parent reply other threads:[~2022-02-03 21:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 19:12 [RFC PATCH 0/4] improve coverage of vector backend Alex Bennée
2022-02-02 19:12 ` [RFC PATCH 1/4] tests/tcg: cleanup sha1 source code Alex Bennée
2022-02-02 21:05 ` Richard Henderson
2022-02-02 19:12 ` [RFC PATCH 2/4] tests/tcg: build sha1-vector for SVE and compare Alex Bennée
2022-02-02 21:09 ` Richard Henderson
2022-02-02 19:12 ` [RFC PATCH 3/4] tests/tcg: add sha512 test Alex Bennée
2022-02-02 21:19 ` Richard Henderson
2022-02-02 19:12 ` [RFC PATCH 4/4] tests/tcg: add vectorised sha512 versions Alex Bennée
2022-02-02 21:18 ` Richard Henderson
2022-02-02 23:16 ` [RFC PATCH 0/4] improve coverage of vector backend Alex Bennée
2022-02-03 1:45 ` Taylor Simpson
2022-02-03 16:33 ` Taylor Simpson
2022-02-03 17:50 ` Alex Bennée
2022-02-03 17:57 ` Taylor Simpson
2022-02-03 18:26 ` Alex Bennée
2022-02-03 19:01 ` Taylor Simpson
2022-02-03 20:00 ` Alex Bennée
2022-02-03 21:05 ` Taylor Simpson
2022-02-03 21:31 ` Richard Henderson [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=b5cfbd97-8f10-c41f-d28d-bf2567585e99@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=tsimpson@quicinc.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 NNTP newsgroup(s).