On 5/27/24 4:17 PM, Jivan Hakobyan wrote:
Ya, makes sense -- I guess the current values aren't that exciting for
execution, but we could just add some more interesting ones...
During the development of the patch, I have an issue with large
numbers (2e34, -2e34). They are used in gfor
>
> Ya, makes sense -- I guess the current values aren't that exciting for
> execution, but we could just add some more interesting ones...
During the development of the patch, I have an issue with large numbers
(2e34, -2e34).
They are used in gfortran.fortran-torture/execute/intrinsic_aint_anint
On Wed, 22 May 2024 12:02:26 PDT (-0700), jeffreya...@gmail.com wrote:
On 5/22/24 12:15 PM, Palmer Dabbelt wrote:
On Wed, 22 May 2024 11:01:16 PDT (-0700), jeffreya...@gmail.com wrote:
On 5/22/24 6:47 AM, Jivan Hakobyan wrote:
After 8367c996e55b2 commit several checks on round_32.c test st
On 5/22/24 12:15 PM, Palmer Dabbelt wrote:
On Wed, 22 May 2024 11:01:16 PDT (-0700), jeffreya...@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 RV3
On Wed, 22 May 2024 11:01:16 PDT (-0700), jeffreya...@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
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:
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: F
