From: Johan Rydberg <johan.rydberg@netinsight.se>
To: lehotsky@earthlink.net
Cc: cgen@sourceware.cygnus.com
Subject: Re: branch-delay slot semantics questions
Date: Fri, 11 May 2001 06:17:00 -0000 [thread overview]
Message-ID: <3AFBE66B.8F75B53C@netinsight.se> (raw)
In-Reply-To: <200105111205.IAA04658@iron.>
lehotsky@earthlink.net wrote:
> Anything I should be looking for? Is there something special my
> mloop.in code needs to do?
I asked the same question a week ago or so, here's my reply from
Frank:
: Anyone got any suggestions how I should implement the delay slot
: handling in the best way?
If you're planning to build a simulator for the gdb/sim collection,
see sim/fr30/mloop.in.
You can follow the thread here:
http://sources.redhat.com/ml/cgen/2001-q2/msg00035.html
regards,
johan
next prev parent reply other threads:[~2001-05-11 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 5:13 lehotsky
2001-05-11 6:17 ` Johan Rydberg [this message]
2001-05-13 15:41 ` Ben Elliston
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=3AFBE66B.8F75B53C@netinsight.se \
--to=johan.rydberg@netinsight.se \
--cc=cgen@sourceware.cygnus.com \
--cc=lehotsky@earthlink.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).