public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug exp/27051] New: maintenance command to show floating point emulation precision
Date: Fri, 11 Dec 2020 13:08:26 +0000	[thread overview]
Message-ID: <bug-27051-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27051

            Bug ID: 27051
           Summary: maintenance command to show floating point emulation
                    precision
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: exp
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I just did commit 9cd7a95a2bb9ba9d5a6af022e5454c8ce78aee56 "[gdb/testsuite] Fix
gdb.base/float128.exp with --with-mpfr=no", where we do:
...
+       if { $mpfr_supported == 0 } {
+          # If the host platform has native 128-bit float support (as is
+          # the case for some versions of s390 and powerpc), the
+          # "print large128" test should be passing, even without MPFR
+          # support.  So, in those cases we should have fail here rather than
+          # unsupported.  However, given that we don't have a way to readily
+          # test for this, we fall back to unsupported.
+          unsupported "$test (Missing MPFR support)"
+       } else {
...

In principle, gdb could make a statement through some maintenance command about
what the expected host-side float point precision is. [ I'm sort of hoping
there already is one, and I haven't found it yet. ]

Then, using this maintenance command we could make this test more accurate.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-12-11 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 13:08 vries at gcc dot gnu.org [this message]
2024-01-10 19:12 ` [Bug exp/27051] " ssbssa at sourceware dot 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-27051-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).