From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "tom@tromey.com" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Kevin Buettner <kevinb@redhat.com>,
"cel@us.ibm.com" <cel@us.ibm.com>
Subject: RE: [PATCH ver 2] PowerPC: fix _Float128 type output string
Date: Tue, 18 Apr 2023 10:17:23 +0000 [thread overview]
Message-ID: <7f54dbb9da74edacb45caffbe90dbfe0d9b4d96a.camel@de.ibm.com> (raw)
In-Reply-To: <87leiqtg94.fsf@tromey.com>
Tom Tromey <tom@tromey.com> wrote:
> >This matters as it changes how GDB prints the type. If your source
> >code has e.g. a variable definition like
> > long double x;
> >and you do e.g. "ptype x" in GDB, you'd expect to see "long double".
> >However, with the GCC hack typedef in place, you actually see
> >"_Float128" instead. This not only confuses the user, it actually
> >causes a bunch of GDB test suite failures currently.
>
>Ok, I understand now. Thank you, & thanks for your patience.
>The patch is OK by me.
Thanks, Tom!
Bye,
Ulrich
prev parent reply other threads:[~2023-04-18 10:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 15:28 [PATCH] " Carl Love
2023-04-05 20:18 ` Carl Love
2023-04-07 21:51 ` Kevin Buettner
2023-04-10 15:43 ` Carl Love
2023-04-10 15:46 ` [PATCH ver 2] " Carl Love
2023-04-10 16:01 ` Carl Love
2023-04-13 14:18 ` Tom Tromey
2023-04-13 16:13 ` Carl Love
2023-04-13 16:35 ` Carl Love
2023-04-13 17:12 ` Tom Tromey
2023-04-13 22:08 ` Carl Love
2023-04-17 15:45 ` [PATCH ver 3] " Carl Love
2023-04-18 10:18 ` Ulrich Weigand
2023-04-14 13:44 ` [PATCH ver 2] " Tom Tromey
2023-04-14 15:35 ` Carl Love
2023-04-17 10:26 ` Ulrich Weigand
2023-04-17 20:17 ` Tom Tromey
2023-04-18 10:17 ` Ulrich Weigand [this message]
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=7f54dbb9da74edacb45caffbe90dbfe0d9b4d96a.camel@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=cel@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=tom@tromey.com \
/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).