public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114140] quadmath fminq/fmaxq with signaling_NaN not work Date: Tue, 27 Feb 2024 22:36:20 +0000 [thread overview] Message-ID: <bug-114140-4-yI7UVlzPPU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114140-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114140 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libquadmath |middle-end --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This has nothing to do quadmath But rather the builtins and constant folding. As shown by: ``` _Float128 f1() { using T = _Float128; //using L = std::numeric_limits<T>; const T a = __builtin_huge_valf128(), b = __builtin_nanf128(""), c = __builtin_nansf128(""); return __builtin_fminf128(a, b); } _Float128 f2() { //using T = std::float128_t; using T = _Float128; // using L = std::numeric_limits<T>; const T a = __builtin_huge_valf128(), b = __builtin_nanf128(""), c = __builtin_nansf128(""); return __builtin_fmaxf128(a, b); } _Float128 f3() { //using T = std::float128_t; using T = _Float128; // using L = std::numeric_limits<T>; const T a = __builtin_huge_valf128(), b = __builtin_nanf128(""), c = __builtin_nansf128(""); return __builtin_fminf128(a, c); } _Float128 f4() { //using T = std::float128_t; using T = _Float128; // using L = std::numeric_limits<T>; const T a = __builtin_huge_valf128(), b = __builtin_nanf128(""), c = __builtin_nansf128(""); return __builtin_fmaxf128(a, c); } ```
next prev parent reply other threads:[~2024-02-27 22:36 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-27 21:09 [Bug libquadmath/114140] New: " g.peterhoff@t-online.de 2024-02-27 22:14 ` [Bug libquadmath/114140] " jakub at gcc dot gnu.org 2024-02-27 22:20 ` jsm28 at gcc dot gnu.org 2024-02-27 22:36 ` pinskia at gcc dot gnu.org [this message] 2024-02-27 22:40 ` [Bug middle-end/114140] fmin/fmax " pinskia at gcc dot gnu.org 2024-02-27 22:41 ` jakub at gcc dot gnu.org 2024-02-27 22:48 ` pinskia at gcc dot gnu.org 2024-02-28 0:59 ` [Bug middle-end/114140] different results for std::fmin/std::fmax and quadmath fminq/fmaxq if one argument=signaling_NaN g.peterhoff@t-online.de 2024-02-28 1:02 ` [Bug libquadmath/114140] " pinskia at gcc dot gnu.org 2024-02-28 1:04 ` pinskia at gcc dot gnu.org 2024-02-28 1:06 ` pinskia at gcc dot gnu.org 2024-02-28 1:07 ` pinskia at gcc dot gnu.org 2024-02-28 1:09 ` pinskia at gcc dot gnu.org 2024-02-28 1:55 ` g.peterhoff@t-online.de 2024-02-28 2:00 ` pinskia at gcc dot gnu.org 2024-02-28 8:12 ` rguenth at gcc dot gnu.org 2024-02-28 11:36 ` xry111 at gcc dot gnu.org 2024-02-28 12:35 ` rguenth at gcc dot gnu.org
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=bug-114140-4-yI7UVlzPPU@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).