From: Andrew Cagney <ac131313@redhat.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: [patch] Add i386_sse_regnum_p() to x86-64-linux-nat..c; Was: [patch] Fix x86-64 build
Date: Fri, 15 Nov 2002 16:12:00 -0000 [thread overview]
Message-ID: <3DD58D76.1080704@redhat.com> (raw)
In-Reply-To: <3DCFD648.1060203@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
> Andrew Cagney wrote:
>
> This quick hack gets around my x86-64 build problem that MarkK pointed out.
>
> Still not perfect... :-((
>
> libgdb.a(x86-64-linux-nat.o)(.text+0x9cc): In function `x86_64_register_u_addr':
> BFD_RELOC_IA64_LTOFF_FPTR64LSB/../../gdb/gdb/x86-64-linux-nat.c:473: undefined reference to `i386_sse_regnum_p'
I've also checked this in (I thought someone would beat me too it).
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 925 bytes --]
2002-11-15 Andrew Cagney <cagney@redhat.com>
* x86-64-linux-nat.c (i386_sse_regnum_p): New function. Copy from
i386-tdep.c.
Index: x86-64-linux-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/x86-64-linux-nat.c,v
retrieving revision 1.17
diff -u -r1.17 x86-64-linux-nat.c
--- x86-64-linux-nat.c 2 Nov 2002 14:59:10 -0000 1.17
+++ x86-64-linux-nat.c 16 Nov 2002 00:10:09 -0000
@@ -456,6 +456,17 @@
#define offsetof(TYPE, MEMBER) ((unsigned long) &((TYPE *)0)->MEMBER)
#endif
+/* SSE register? */
+/* FIXME: cagney/2002-11-15: Once the i386 and x86-64 are integrated,
+ this will go. */
+
+int
+i386_sse_regnum_p (int regnum)
+{
+ return (regnum < NUM_REGS
+ && (XMM0_REGNUM <= (regnum) && (regnum) < MXCSR_REGNUM));
+}
+
/* Return the address of register REGNUM. BLOCKEND is the value of
u.u_ar0, which should point to the registers. */
CORE_ADDR
prev parent reply other threads:[~2002-11-16 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 8:00 Andrew Cagney
2002-11-11 8:09 ` Michal Ludvig
2002-11-15 16:12 ` Andrew Cagney [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=3DD58D76.1080704@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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