This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Detecting and printing 128-bit long double values for PPC
- From: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- To: drow at false dot org (Daniel Jacobowitz)
- Cc: luisgpm at linux dot vnet dot ibm dot com (Luis Machado), gdb-patches at sourceware dot org (gdb-patches ml)
- Date: Sat, 28 Apr 2007 18:24:14 +0200 (CEST)
- Subject: Re: [RFC] Detecting and printing 128-bit long double values for PPC
Daniel Jacobowitz wrote:
> Unfortunately most of Mark's comments are still unaddressed. The
> formatting doesn't follow the GNU coding standards, and the real
> issue with this patch is that there are a lot of systems out in the
> world that use 64-bit long double still.
>
> I mentioned last week on gdb@ and binutils@ that I think we need a way
> to mark the ABI used by PowerPC binaries. That would easily cover
> this also. I'll be thinking about it more next week.
We have the same situation on s390, where we switched from 64-bit to
128-bit long double a while ago. Like PowerPC, there is currently no
way to recognize how a binary was built ...
While an ABI marker might be a good idea in the future, we're stuck
with the situation right now that many unmarked 128-bit long double
binaries are already out there (e.g. all of SLES 10 and RHEL 5),
and we really should be able to debug those properly.
Thus I'm wondering whether we shouldn't have a reasonable default
for unmarked binaries, presumably based on the system compiler
defaults detected at configure time for native builds, and then
provide a command allowing the user to override that default?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com