From: Joseph A <joseph.altmaier@gmail.com>
To: cgen@sourceware.org
Subject: Re: Delayed Memory Writes
Date: Tue, 04 Aug 2009 18:58:00 -0000 [thread overview]
Message-ID: <24814271.post@talk.nabble.com> (raw)
In-Reply-To: <20090804174448.GG12318@redhat.com>
Frank Ch. Eigler wrote:
>
>
> It nests the other way:
>
> (delay 1 (set FOO BAR))
>
> - FChE
>
>
When nested this way I get the error
"ERROR: In procedure string-append:
ERROR: Wrong type argument (expecting STRINGP): set"
The code
(set (delay 2 (reg SI h-gr r)) a)
works fine, as do delayed sets of hardware other than memory. The error
only appears when I try to do a delayed memory set. The mt port uses delays
nested in this manner, and the sh port uses delays nested in the manner you
suggested. I'm a little confused. Are they both valid? Perhaps I'm using
an old version?
Thanks
Joseph
--
View this message in context: http://www.nabble.com/Delayed-Memory-Writes-tp24813100p24814271.html
Sent from the Sourceware - cgen list mailing list archive at Nabble.com.
prev parent reply other threads:[~2009-08-04 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 17:38 Joseph A
2009-08-04 17:51 ` Frank Ch. Eigler
2009-08-04 18:58 ` Joseph A [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=24814271.post@talk.nabble.com \
--to=joseph.altmaier@gmail.com \
--cc=cgen@sourceware.org \
/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).