public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: jeffreyalaw@gmail.com
Cc: jivanhakobyan9@gmail.com, gcc-patches@gcc.gnu.org,
	Jeff Law <jlaw@ventanamicro.com>
Subject: Re: RISC-V: Fix round_32.c test on RV32
Date: Wed, 22 May 2024 11:15:29 -0700 (PDT)	[thread overview]
Message-ID: <mhng-6b57f65b-afb2-4fc4-9c00-8d93c21aa543@palmer-ri-x1c9> (raw)
In-Reply-To: <a9dd7d3d-8025-4838-a3fb-b7fcc7403985@gmail.com>

On Wed, 22 May 2024 11:01:16 PDT (-0700), jeffreyalaw@gmail.com wrote:
>
>
> On 5/22/24 6:47 AM, Jivan Hakobyan wrote:
>> After 8367c996e55b2 commit several checks on round_32.c test started to
>> fail.
>> The reason is that we prevent rounding DF->SI->DF on RV32 and instead of
>> a conversation sequence we get calls to appropriate library functions.
>>
>>
>> gcc/testsuite/ChangeLog:
>>          * testsuite/gcc.target/riscv/round_32.c: Fixed test
> I wonder if this test even makes sense for rv32 anymore given we can't
> do a DF->DI as a single instruction and DF->SI is going to give
> incorrect results.  So the underlying optimization to improve those
> rounding cases just doesn't apply to DF mode objects for rv32.
>
> Thoughts?

Unless I'm missing something, we should still be able to do the 
float roundings on rv32?

I think with Zfa we'd also have testable sequences for the double/double 
and float/float roundings, which could be useful to test.  I'm not 
entirely sure there, though, as I always get a bit lost in which FP 
rounding flavors map down.

I'd also kicked off some run trying to promote these to executable 
tests.   IIRC it was just DG stuff (maybe just adding a `dg-do run`?) 
but I don't know where I stashed the results...

> Jeff

  reply	other threads:[~2024-05-22 18:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 12:47 Jivan Hakobyan
2024-05-22 18:01 ` Jeff Law
2024-05-22 18:15   ` Palmer Dabbelt [this message]
2024-05-22 19:02     ` Jeff Law
2024-05-22 19:19       ` Palmer Dabbelt
2024-05-27 22:17         ` Jivan Hakobyan
2024-06-01  5:03           ` Jeff Law

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=mhng-6b57f65b-afb2-4fc4-9c00-8d93c21aa543@palmer-ri-x1c9 \
    --to=palmer@dabbelt.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=jivanhakobyan9@gmail.com \
    --cc=jlaw@ventanamicro.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).