public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "g.peterhoff@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libquadmath/114140] New: quadmath fminq/fmaxq with signaling_NaN not work
Date: Tue, 27 Feb 2024 21:09:36 +0000	[thread overview]
Message-ID: <bug-114140-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114140

            Bug ID: 114140
           Summary: quadmath fminq/fmaxq with signaling_NaN not work
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libquadmath
          Assignee: unassigned at gcc dot gnu.org
          Reporter: g.peterhoff@t-online.de
  Target Milestone: ---

please see https://godbolt.org/z/T4W8Mejxz

Notes:
* std::numeric_limits<__float128> (from boost) does not work properly, so I
fall back to builtins.
* std::fmin/fmax for __float128 calls fminq/fmaxq (boost, this works)

thx
Gero

             reply	other threads:[~2024-02-27 21:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 21:09 g.peterhoff@t-online.de [this message]
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 ` [Bug middle-end/114140] " pinskia at gcc dot gnu.org
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@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: 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).