From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [patch] Fix x86-64 build
Date: Mon, 11 Nov 2002 08:00:00 -0000 [thread overview]
Message-ID: <3DCFD40C.9020906@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 103 bytes --]
Hello,
This quick hack gets around my x86-64 build problem that MarkK pointed out.
Committed,
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 963 bytes --]
2002-11-11 Andrew Cagney <ac131313@redhat.com>
* x86-64-tdep.c (i386_fp_regnum_p): Copy i386-tdep.c's
i386_fp_regnum_p.
Index: gdb/x86-64-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/x86-64-tdep.c,v
retrieving revision 1.36
diff -u -r1.36 x86-64-tdep.c
--- gdb/x86-64-tdep.c 2 Nov 2002 14:59:10 -0000 1.36
+++ gdb/x86-64-tdep.c 11 Nov 2002 15:49:47 -0000
@@ -175,6 +175,15 @@
return *x86_64_register_info_table[regno].type;
}
+/* FIXME: cagney/2002-11-11: Once the i386 and x86-64 targets are
+ merged, this function can go away. */
+int
+i386_fp_regnum_p (int regnum)
+{
+ return (regnum < NUM_REGS
+ && (FP0_REGNUM && FP0_REGNUM <= (regnum) && (regnum) < FPC_REGNUM));
+}
+
/* x86_64_register_convertible is true if register N's virtual format is
different from its raw format. Note that this definition assumes
that the host supports IEEE 32-bit floats, since it doesn't say
next reply other threads:[~2002-11-11 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 8:00 Andrew Cagney [this message]
2002-11-11 8:09 ` Michal Ludvig
2002-11-15 16:12 ` [patch] Add i386_sse_regnum_p() to x86-64-linux-nat..c; Was: " Andrew Cagney
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=3DCFD40C.9020906@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