From: Branislav Brzak <Branislav.Brzak@Syrmia.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Dragoslav Sicarov <Dragoslav.Sicarov@Syrmia.com>,
Djordje Todorovic <Djordje.Todorovic@syrmia.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH 0/2] riscv: Fix gas when encoding BE floats/doubles
Date: Thu, 15 Jun 2023 12:14:14 +0000 [thread overview]
Message-ID: <AM6PR03MB4984EDF2131CE06BD878814B985BA@AM6PR03MB4984.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <a8e74f07-04e0-4a2b-8a50-9756a339da52@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
Hi,
I wasn't aware of that patch. The only difference between
my patch and Andreas are that I have added tests to test
encoding of doubles as well as float ones.
Regards,
Branislav
________________________________
From: Jan Beulich <jbeulich@suse.com>
Sent: Thursday, June 15, 2023 2:09 PM
To: Branislav Brzak <Branislav.Brzak@Syrmia.com>
Cc: Dragoslav Sicarov <Dragoslav.Sicarov@Syrmia.com>; Djordje Todorovic <Djordje.Todorovic@syrmia.com>; binutils@sourceware.org <binutils@sourceware.org>
Subject: Re: [PATCH 0/2] riscv: Fix gas when encoding BE floats/doubles
On 15.06.2023 13:09, Branislav Brzak wrote:
> RISCV gas currently does not take into consideration -mbig-endian
> directive when encoding floats and doubles. The effect is that when
> -mbig-endian is supplied floats and doubles are endian flipped only
> on 2-byte boundaries, for example:
>
> .data:
> .float 1.1
>
> Compiled as LE will be encoded as: 0xcdcc8c3f
> And BE encoded will be: 0x8c3fcdcc
>
> The correct sequence is 0x3f8ccccd
>
> This patch introduces a fix in float/double endian encoding and
> set of tests that verify validity of LE and BE float and double
> encoding.
>
> Branislav Brzak (2):
> gas: Fix float/double BE encoding in RISCV.
> riscv: Add LE/BE float/double encoding tests.
>
> gas/config/tc-riscv.c
> gas/testsuite/gas/riscv/double-be.d | 18 ++++++++++++++++++
> gas/testsuite/gas/riscv/double-le.d | 18 ++++++++++++++++++
> gas/testsuite/gas/riscv/double.s | 21 +++++++++++++++++++++
> gas/testsuite/gas/riscv/float-be.d | 13 +++++++++++++
> gas/testsuite/gas/riscv/float-le.d | 13 +++++++++++++
> gas/testsuite/gas/riscv/float.s | 21 +++++++++++++++++++++
> 7 files changed, 105 insertions(+), 1 deletion(-)
Did you see
https://sourceware.org/pipermail/binutils/2023-June/127845.html
? (Only the cover letter came through so far, so I can't tell yet
whether you do anything different than Andreas does. Also, as an
aside, it typically helps if you Cc arch maintainers for arch
patches.)
Jan
next prev parent reply other threads:[~2023-06-15 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 11:09 Branislav Brzak
2023-06-15 12:09 ` Jan Beulich
2023-06-15 12:14 ` Branislav Brzak [this message]
2023-06-16 0:38 ` Nelson Chu
2023-06-19 7:18 ` Andreas Schwab
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=AM6PR03MB4984EDF2131CE06BD878814B985BA@AM6PR03MB4984.eurprd03.prod.outlook.com \
--to=branislav.brzak@syrmia.com \
--cc=Djordje.Todorovic@syrmia.com \
--cc=Dragoslav.Sicarov@Syrmia.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).