From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Daniel Cederman <cederman@gaisler.com>, libc-alpha@sourceware.org
Cc: daniel@gaisler.com, andreas@gaisler.com
Subject: Re: [PATCH] sparc: Fix llrint and llround missing exceptions on SPARC32
Date: Mon, 15 Jan 2024 14:52:03 -0300 [thread overview]
Message-ID: <1d21ad55-83f7-4031-96bf-a0b6db5f1959@linaro.org> (raw)
In-Reply-To: <48a9eff3-7776-43d4-b316-06a70d5b6670@gaisler.com>
On 15/01/24 11:38, Daniel Cederman wrote:
> On 2024-01-12 19:05, Adhemerval Zanella Netto wrote:
>>
>>
>> On 12/01/24 06:26, Daniel Cederman wrote:
>>> +/* Define these macros to 1 to workaround conversions of out-of-range
>>> + floating-point numbers to integer types failing to raise the
>>> + "invalid" exception, or raising spurious "inexact" or other
>>> + exceptions. */
>>
>> This is not really true for all sparc32, at least with sparcv9 I have
>> access I have not seen any issues with missing exception overflows or
>> spurious inexact. Are these some leon3 limitation or issue?
>>
>
> I don't think it is a leon specific issue. I can trigger the same issue with QEMU for other sparcs. Sparcv9 has custom versions of the functions involved so that is probably why it is not affected:
>
> ./sysdeps/sparc/sparc32/sparcv9/fpu/multiarch/s_llrint.c
> ./sysdeps/sparc/sparc32/sparcv9/fpu/multiarch/s_llrintf.c
>
> Corresponding patches for other 32-bit architectures references this bugzilla entry:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59412
>
> I will have to look into this again, but I remember that it was a similar issue for sparc32.
You are right that sparcv9 has assembly specific implementation, but even
though by removing them and forcing libm to use the generic implementation
I am not seeing any regression.
I almost sure it is because on sparcv9, compile generates fdtox for double
to interger which is not subject to overflow issues.
>
>> I think we need to know exactly how/when this happens and only enable
>> such workaound when required.
>>
>>> +#define FIX_FLT_LONG_CONVERT_OVERFLOW 0
>>> +#define FIX_FLT_LLONG_CONVERT_OVERFLOW 1
>>> +#define FIX_DBL_LONG_CONVERT_OVERFLOW 0
>>> +#define FIX_DBL_LLONG_CONVERT_OVERFLOW 1
>>> +#define FIX_LDBL_LONG_CONVERT_OVERFLOW 0
>>> +#define FIX_LDBL_LLONG_CONVERT_OVERFLOW 0
>>> +#define FIX_FLT128_LONG_CONVERT_OVERFLOW 0
>>> +#define FIX_FLT128_LLONG_CONVERT_OVERFLOW 0
>>> +
>>> +#endif /* fix-fp-int-convert-overflow.h */
So I think it should be something like:
#define FIX_FLT_LONG_CONVERT_OVERFLOW 0
#define FIX_DBL_LONG_CONVERT_OVERFLOW 0
#define FIX_LDBL_LONG_CONVERT_OVERFLOW 0
#define FIX_LDBL_LLONG_CONVERT_OVERFLOW 0
#define FIX_FLT128_LONG_CONVERT_OVERFLOW 0
#define FIX_FLT128_LLONG_CONVERT_OVERFLOW 0
/* For sparcv9 compiler generates fdtox/fstox for floating point to
integer generation. */
#ifdef __sparcv9
# define FIX_FLT_LLONG_CONVERT_OVERFLOW 0
# define FIX_DBL_LLONG_CONVERT_OVERFLOW 0
#else
# define FIX_FLT_LLONG_CONVERT_OVERFLOW 1
# define FIX_DBL_LLONG_CONVERT_OVERFLOW 1
#endif
Even though it is not used currently on code generation.
next prev parent reply other threads:[~2024-01-15 17:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 9:26 [PATCH] sparc: Do not test preservation of NaN payloads for LEON Daniel Cederman
2024-01-12 9:26 ` [PATCH] sparc: Prevent stfsr from directly following floating-point instruction Daniel Cederman
2024-01-12 14:38 ` Adhemerval Zanella Netto
2024-01-15 9:37 ` Daniel Cederman
2024-01-12 9:26 ` [PATCH] sparc: Force calculation that raises exception Daniel Cederman
2024-01-12 16:45 ` Adhemerval Zanella Netto
2024-01-15 9:41 ` Daniel Cederman
2024-01-15 11:47 ` Adhemerval Zanella Netto
2024-01-12 9:26 ` [PATCH] sparc: Treat the version field in the FPU control word as reserved Daniel Cederman
2024-01-12 17:42 ` Adhemerval Zanella Netto
2024-02-15 9:31 ` Daniel Cederman
2024-02-19 14:55 ` Adhemerval Zanella Netto
2024-01-12 9:26 ` [PATCH] sparc: Fix llrint and llround missing exceptions on SPARC32 Daniel Cederman
2024-01-12 18:05 ` Adhemerval Zanella Netto
2024-01-15 14:38 ` Daniel Cederman
2024-01-15 17:52 ` Adhemerval Zanella Netto [this message]
2024-01-12 9:26 ` [PATCH] sparc: Remove unwind information from signal return stub functions Daniel Cederman
2024-01-15 13:41 ` Adhemerval Zanella Netto
2024-01-15 14:22 ` Daniel Cederman
2024-01-15 16:57 ` Adhemerval Zanella Netto
2024-01-16 15:37 ` [PATCH] sparc: Do not test preservation of NaN payloads for LEON Adhemerval Zanella Netto
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=1d21ad55-83f7-4031-96bf-a0b6db5f1959@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=andreas@gaisler.com \
--cc=cederman@gaisler.com \
--cc=daniel@gaisler.com \
--cc=libc-alpha@sourceware.org \
/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).