public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/31282] [gdb/fortran] logical type doesn't match documentation of TYPE_CODE_BOOL
Date: Wed, 24 Jan 2024 16:58:08 +0000	[thread overview]
Message-ID: <bug-31282-4717-3PxX1CS5Im@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31282-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom de Vries from comment #3)
> (In reply to Tom Tromey from comment #1)
> > It's also worth considering how hardbool should work.
> 
> Ah, interesting, thanks.  I found some explanation here (
> https://gcc.gnu.org/onlinedocs/gnat_rm/Hardened-Booleans.html ).

For Ada it probably isn't such a big issue, due to how Ada's
type system works -- the compiler is already equipped to
think of things as enums and ranges and whatnot.

However hardbool is also a C extension feature now.
Search for "hardbool" here:
https://gcc.gnu.org/gcc-14/changes.html

Anyway I think gdb is at the mercy of the compiler(s) here.
It's not unreasonable to expect them to tell gdb what
the bool values are; and if this can't be expressed in DWARF,
then a DWARF update is also required.

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

  parent reply	other threads:[~2024-01-24 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 20:27 [Bug fortran/31282] New: " vries at gcc dot gnu.org
2024-01-24  1:10 ` [Bug fortran/31282] " tromey at sourceware dot org
2024-01-24 11:11 ` vries at gcc dot gnu.org
2024-01-24 12:16 ` vries at gcc dot gnu.org
2024-01-24 13:49 ` vries at gcc dot gnu.org
2024-01-24 16:58 ` tromey at sourceware dot org [this message]
2024-01-25 12:29 ` vries at gcc dot gnu.org
2024-01-25 14:57 ` tromey 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-31282-4717-3PxX1CS5Im@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).