From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: scm_remember_upto_here asm volatile
Date: Tue, 26 Aug 2003 09:48:10 +1000 [thread overview]
Message-ID: <87r8398fk5.fsf@zip.com.au> (raw)
In-Reply-To: <3F4742BD.9090704@dirk-herrmanns-seiten.de> (Dirk Herrmann's message of "Sat, 23 Aug 2003 12:32:29 +0200")
Dirk Herrmann <dirk@dirk-herrmanns-seiten.de> writes:
>
> would you mind to add an explanation of the syntax of that construct?
> For example, what does the "g" mean? Since we don't have many asm
> instructions in guile, it is fair to assume that most of the
> developers don't know about the exact meaning of that construct.
How about the tweak below. No doubt the gcc manual describes the
overall syntax better than a bit of a comment could do, the aim I
guess would be just to cover the reasoning for why this form does
what's wanted in this context.
/* In GCC we can force a reference to an SCM with a little do-nothing asm,
avoiding the code size and slowdown of an actual function call.
Unfortunately there doesn't seem to be any way to do the varargs
scm_remember_upto_here similarly.
__volatile__ ensures nothing will be moved across the asm, and it won't
be optimized away (or only if proved unreachable). Constraint "g" can be
used on all processors, it allows any memory, general register, or
immediate operand. The actual asm syntax which comes out for it doesn't
matter, we don't want to use it, just ensure the operand is still
alive. */
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-08-25 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 22:19 scm_remember_upto_here asm volatile Kevin Ryde
2003-05-17 20:26 ` Marius Vollmer
2003-05-19 0:24 ` Kevin Ryde
2003-06-01 18:47 ` Marius Vollmer
2003-06-01 19:29 ` Mikael Djurfeldt
2003-08-13 21:09 ` Kevin Ryde
2003-08-23 10:32 ` Dirk Herrmann
2003-08-25 23:48 ` Kevin Ryde [this message]
2003-08-27 4:28 ` Dirk Herrmann
2003-08-27 23:49 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r8398fk5.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.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).