From: Kevin Buettner <kevinb@redhat.com>
To: Dave Brolley <brolley@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] FR-V SIM: Check availability of GR and FR regs
Date: Fri, 07 Nov 2003 17:49:00 -0000 [thread overview]
Message-ID: <1031107174924.ZM17946@localhost.localdomain> (raw)
In-Reply-To: Dave Brolley <brolley@redhat.com> "Re: [RFA] FR-V SIM: Check availability of GR and FR regs" (Nov 7, 12:30pm)
On Nov 7, 12:30pm, Dave Brolley wrote:
> I'm not sure if it's ok to include gdb/sim-frv.h from within the
> simulator code. I thought the interface went the other way around (i.e.
> gdb includes sim/frv-sim.h).
Keep in mind that gdb/sim-frv.h is actually include/gdb/sim-frv.h.
This file contains only those register numbers which are needed for
sim <-> gdb interactions. The file sim/frv-sim.h contains quite a lot
more. I'd be more than a little nervous including it in gdb's
frv-tdep.c.
Before embarking on this course, I did check for precedents. Here's
what I found:
sim/sh64/sh64.c[34]: #include "gdb/sim-sh.h"
sim/sh/interp.c[32]: #include "gdb/sim-sh.h"
sim/h8sx/compile.c[33]: #include "gdb/sim-h8300.h"
sim/h8300/compile.c[33]: #include "gdb/sim-h8300.h"
sim/d10v/interp.c[8]: #include "gdb/sim-d10v.h"
sim/arm/wrapper.c[39]: #include "gdb/sim-arm.h"
> Other than that, it looks ok to me.
I'll wait until we've resolved the above to commit it.
Kevin
next prev parent reply other threads:[~2003-11-07 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 6:33 Kevin Buettner
2003-11-07 17:30 ` Dave Brolley
2003-11-07 17:49 ` Kevin Buettner [this message]
2003-11-07 19:12 ` Michael Snyder
2003-11-24 16:47 ` Kevin Buettner
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=1031107174924.ZM17946@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=brolley@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