https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #7 from joseph at codesourcery dot com ---
There shouldn't be such a thing as an unsupported constant payload; both
__builtin_nan and __builtin_nans should rather be made consistent with
parsing of payloads by glibc's nan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #6 from Xi Ruoyao ---
(In reply to jos...@codesourcery.com from comment #5)
> We should absolutely *not* generate calls to a non-existent function
> "nans" based on a long-obsolescent standard proposal. The modern way to
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #5 from joseph at codesourcery dot com ---
We should absolutely *not* generate calls to a non-existent function
"nans" based on a long-obsolescent standard proposal. The modern way to
generate a signaling NaN with given payload,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #4 from chenxiaolong ---
(In reply to chenxiaolong from comment #3)
> //test.c
> #include
>
> int main(void)
> {
> _Float128 ret=__builtin_nansf128("NAN");
> printf("ret=%Lf\n",ret);
>
> return 0;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
chenxiaolong changed:
What|Removed |Added
CC||chenxiaolong at loongson dot cn
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #2 from Andrew Pinski ---
Newer version of that paper:
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1011.htm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-18
Ever confirmed|0
