Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [obish] fix solaris 8 sparc-tdep.c compile problem
Date: Wed, 30 Apr 2003 20:31:00 -0000	[thread overview]
Message-ID: <3EB013D5.6090607@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 167 bytes --]

This fixes a compile problem for solaris 8 (SPARC).  I'm not yet sure if 
it fixes a build though - I got a link error from using a really old 
compiler :-(

Andrew



[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 938 bytes --]

2003-04-30  Andrew Cagney  <cagney@redhat.com>

	* sparc-tdep.c (SPARC_HAS_FPU): When multi-arch, define as 1.

Index: sparc-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/sparc-tdep.c,v
retrieving revision 1.92
diff -u -r1.92 sparc-tdep.c
--- sparc-tdep.c	29 Apr 2003 01:49:47 -0000	1.92
+++ sparc-tdep.c	30 Apr 2003 18:16:44 -0000
@@ -51,8 +51,11 @@
 
 #if (GDB_MULTI_ARCH > 0)
 
-/* Does the target have Floating Point registers?  */
-#define SPARC_HAS_FPU     (gdbarch_tdep (current_gdbarch)->has_fpu)
+#if 0
+// OBSOLETE /* Does the target have Floating Point registers?  */
+// OBSOLETE #define SPARC_HAS_FPU     (gdbarch_tdep (current_gdbarch)->has_fpu)
+#endif
+#define SPARC_HAS_FPU 1
 /* Number of bytes devoted to Floating Point registers: */
 #define FP_REGISTER_BYTES (gdbarch_tdep (current_gdbarch)->fp_register_bytes)
 /* Highest numbered Floating Point register.  */

             reply	other threads:[~2003-04-30 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 20:31 Andrew Cagney [this message]
2003-04-30 22:01 ` Joel Brobecker
2003-04-30 22:10 ` Joel Brobecker

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=3EB013D5.6090607@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.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