From: Andrew Cagney <ac131313@cygnus.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Will Cohen <wcohen@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Patch to provide m68k simulator to gdb
Date: Fri, 09 Mar 2001 12:54:00 -0000 [thread overview]
Message-ID: <3AA63AB7.123C81FD@cygnus.com> (raw)
In-Reply-To: <o5u2566ab3.fsf@toenail.toronto.redhat.com>
"Frank Ch. Eigler" wrote:
>
> Will Cohen <wcohen@redhat.com> writes:
>
> : [...]
> : > If these are the register numbers being passed in via
> : > sim_{fetch,store}_register() then they should be defined
> : > include/sim-m68k.h.
> :
> : If that's the way to do it okay. I only saw include/sim-d10v.h there.
> : None of the other simulators followed this approach. I was emulating
> : what I saw in the vast majority of the simulators.
>
> FWIW, I agree with Will. The sim-d10v.h, while not a bad idea, is a
> very lonely and rather old precedent to become required of new ports.
FYI, That file was only introduced a year ago. It occured when the d10v
was given an upgrade. I've been pretty consistent in asking anyone with
a new simulator (merged or not) to follow that convention.
Andrew
next prev parent reply other threads:[~2001-03-09 12:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 14:59 Will Cohen
2001-02-27 15:35 ` J.T. Conklin
2001-02-28 8:02 ` Andrew Cagney
2001-02-28 8:58 ` Will Cohen
2001-02-28 9:17 ` Andrew Cagney
2001-03-05 13:12 ` Will Cohen
2001-02-28 8:39 ` Andrew Cagney
2001-02-28 9:01 ` Will Cohen
2001-03-01 11:24 ` Will Cohen
2001-03-01 11:54 ` Andrew Cagney
2001-03-05 13:25 ` Will Cohen
2001-03-05 14:57 ` Andrew Cagney
2001-03-06 8:22 ` Will Cohen
2001-03-06 10:07 ` Frank Ch. Eigler
2001-03-09 12:54 ` Andrew Cagney [this message]
2001-03-05 15:12 ` Andrew Cagney
2001-03-06 10:11 ` Frank Ch. Eigler
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=3AA63AB7.123C81FD@cygnus.com \
--to=ac131313@cygnus.com \
--cc=fche@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=wcohen@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