Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gdb-patches@sourceware.org
Subject: [PATCH]: Remove sparc-linux long double size override.
Date: Mon, 12 May 2008 16:01:00 -0000	[thread overview]
Message-ID: <20080511.151940.173655400.davem@davemloft.net> (raw)


We realized many years ago that using 64-bit long doubles
for 32-bit sparc was a mistake and migrated all of userland
over to using proper 128-bit long doubles.

There isn't a way to really detect this at run time, but I
think it's better to move forward and delete this override
and get current systems right rather than support ancient
ones.

This fixes another swath of testsuite failures.

Ok to apply?

2008-05-11  David S. Miller  <davem@davemloft.net>

	* sparc-linux-tdep.c (sparc32_linux_init_abi): Remove
	long double size override, Linux does use 128-bit now.

Index: gdb/sparc-linux-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/sparc-linux-tdep.c,v
retrieving revision 1.27
diff -u -r1.27 sparc-linux-tdep.c
--- gdb/sparc-linux-tdep.c	11 May 2008 22:10:30 -0000	1.27
+++ gdb/sparc-linux-tdep.c	11 May 2008 22:16:42 -0000
@@ -264,10 +264,6 @@
      prologue analysis.  */
   tdep->plt_entry_size = 12;
 
-  /* GNU/Linux doesn't support the 128-bit `long double' from the psABI.  */
-  set_gdbarch_long_double_bit (gdbarch, 64);
-  set_gdbarch_long_double_format (gdbarch, floatformats_ieee_double);
-
   /* Enable TLS support.  */
   set_gdbarch_fetch_tls_load_module_address (gdbarch,
                                              svr4_fetch_objfile_link_map);


             reply	other threads:[~2008-05-11 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 16:01 David Miller [this message]
2008-05-12 16:38 ` Daniel Jacobowitz
2008-05-12 19:46   ` David Miller

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=20080511.151940.173655400.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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