From: Ben Elliston <bje@redhat.com>
To: cgd@sibyte.com (Chris G. Demetriou)
Cc: cagney@cygnus.com, gdb@sources.redhat.com
Subject: Re: [sim/mips] Proposed change to mips_core_signal
Date: Mon, 12 Feb 2001 21:27:00 -0000 [thread overview]
Message-ID: <14984.50602.977447.12874@scooby.cygnus.com> (raw)
In-Reply-To: <yov5wvav46b8.fsf@highland.sibyte.com>
Chris G. Demetriou writes:
> > I am working on a simulator port to a MIPS-like core that has a vector
> > processing unit. To produce more helpful diagnostic messages, it
> > would useful if mips_core_signal() could differentiate between scalar
> > memory transfers and vector memory transfers.
> > Are there any objections to adding two new elements to the
> > _transfer_type enum in sim-basics.h to identify such transfers?
> I have no problem with it, but it's not clear that I know enough to
> object.
I've found a cleaner way of implementing this that does not affect
sim/common code. Forget this thread ever existed!
Cheers, Ben
prev parent reply other threads:[~2001-02-12 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 14:35 Ben Elliston
2001-02-12 19:21 ` Chris G. Demetriou
2001-02-12 19:39 ` Ben Elliston
2001-02-12 21:27 ` Ben Elliston [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=14984.50602.977447.12874@scooby.cygnus.com \
--to=bje@redhat.com \
--cc=cagney@cygnus.com \
--cc=cgd@sibyte.com \
--cc=gdb@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