From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, AlokKumar.Sharma@amd.com
Subject: Re: [PATCHv2] gdb/fortran: Fix printing of logical true values for Flang
Date: Tue, 03 Mar 2020 16:32:00 -0000 [thread overview]
Message-ID: <87pndtcsck.fsf@tromey.com> (raw)
In-Reply-To: <20200302182152.12819-1-andrew.burgess@embecosm.com> (Andrew Burgess's message of "Mon, 2 Mar 2020 18:21:52 +0000")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> Thanks for looking into this. I think that the best solution right
Andrew> now will be to handle TYPE_CODE_BOOL in f_val_print rather than
Andrew> modifying generic_val_print_bool.
Agreed.
Andrew> The other possibility would be, I think, to add a new field to 'struct
Andrew> language_defn' and use this in generic_val_print_bool instead of
Andrew> comparing the value of current_lanuage directly, however, this isn't
Andrew> the common approach, so I'd prefer to handle this case just like other
Andrew> TYPE_CODE_* are handled for now.
It would be nice if we could get away from having separate printing code
for each language. I don't know how practical this is though.
Andrew> I know that in places within GDB we do compare the value of
Andrew> current_lanuage to the know language structures, but I'd like to move
Andrew> us away from doing this.
Also agreed.
Tom
next prev parent reply other threads:[~2020-03-03 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 17:00 [PATCH] gdb/fortran Fixed " Sharma, Alok Kumar
2020-03-02 18:21 ` [PATCHv2] gdb/fortran: Fix " Andrew Burgess
2020-03-03 4:47 ` Sharma, Alok Kumar
2020-03-03 18:21 ` Andrew Burgess
2020-03-04 8:48 ` [gdb/testsuite] Fix missing uint8_t in gdb.fortran/logical.exp Tom de Vries
2020-03-11 10:24 ` Andrew Burgess
2020-03-11 12:00 ` Tom de Vries
2020-03-03 16:32 ` Tom Tromey [this message]
2020-03-03 17:24 ` [PATCHv2] gdb/fortran: Fix printing of logical true values for Flang Andrew Burgess
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=87pndtcsck.fsf@tromey.com \
--to=tom@tromey.com \
--cc=AlokKumar.Sharma@amd.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@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