From: Ben Elliston <bje@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: cgen@sources.redhat.com
Subject: Re: Confusion: setup-semantics? PC not updated? Immediate operands?
Date: Tue, 29 Jan 2002 17:47:00 -0000 [thread overview]
Message-ID: <15447.20614.371737.126875@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <200201290003.BAA12296@ignucius.axis.se>
H-P,
>>>>> "Hans-Peter" == Hans-Peter Nilsson <hans-peter.nilsson@axis.com> writes:
Hans-Peter> This when generating that big GCC-specific C switch
Hans-Peter> <arch>-switch.c, which seems generated from sim-cpu.scm. From
Hans-Peter> what little scheme I understand (I'm blissfully naive), it seems
Hans-Peter> only sid-cpu.scm, not sim-cpu.scm, supports setup-semantics.
Hans-Peter> I'd use it for purposes similar to that of arm.cpu.
Hans-Peter> Should it work?
I think you are correct. The setup-semantics work might need to be
back-ported to sim-cpu.scm. Much of the work is completely analogous;
it shouldn't be too difficult.
arm.cpu was the first port to use setup-semantics and back then, we
were doing early SID component development. The ARM was our first
hw-cpu-* component, which would explain why setup-semantics is only
supported by sid-cpu.scm.
Ben
next prev parent reply other threads:[~2002-01-30 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 16:03 Hans-Peter Nilsson
2002-01-29 17:47 ` Ben Elliston [this message]
2002-01-29 18:34 ` Hans-Peter Nilsson
2002-01-29 20:06 ` Frank Ch. Eigler
2002-01-30 7:10 ` Hans-Peter Nilsson
2002-03-20 16:47 ` [RFA:] support setup-semantics in sim-cpu.scm (was: Re: Confusion: setup-semantics? ...) Hans-Peter Nilsson
2002-04-18 15:20 ` Hans-Peter Nilsson
2002-06-19 15:46 ` [RFA:] support setup-semantics in sim-cpu.scm Hans-Peter Nilsson
2002-03-22 9:16 ` Confusion: setup-semantics? PC not updated? Immediate operands? Doug Evans
2002-03-22 9:20 ` Doug Evans
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=15447.20614.371737.126875@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=hans-peter.nilsson@axis.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).