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 fortran/31282] [gdb/fortran] logical type doesn't match documentation of TYPE_CODE_BOOL
Date: Wed, 24 Jan 2024 13:49:37 +0000 [thread overview]
Message-ID: <bug-31282-4717-D4mTAtHnix@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 #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #1)
> Updating the comment seems fine.
In gdbtypes.c I found:
...
std::optional<LONGEST>
get_discrete_low_bound (struct type *type)
{
...
case TYPE_CODE_BOOL:
return 0;
...
and:
...
std::optional<LONGEST>
get_discrete_high_bound (struct type *type)
{
case TYPE_CODE_BOOL:
return 1;
...
...
So, the notion the comment describes seems to be hardcoded in the code.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-24 13:49 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 [this message]
2024-01-24 16:58 ` tromey at sourceware dot org
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-D4mTAtHnix@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).