From: pip pip@cpu.khimaira.com
Subject: [9fans] TAS
Date: Sat, 19 Jun 1999 11:52:02 -0400 [thread overview]
Message-ID: <19990619155202.vobGUQCd-FWL1YqAHi4GraMGao-E7B28nfqXMg_tD8A@z> (raw)
On Sat, 19 Jun 1999, Nigel Roles wrote:
>>> Why implement as a call? Because inlining is not supported by the
>>> compiler,
I think you may have misunderstood what I meant when I said 'inline'. I
did not mean like gcc's __inline__ or C++ inline fxns. I meant doing it
maually.
>>> anyway the instruction sequence has a very strong chance of being
>>> cached as it is used a lot, so performance is not really an issue.
???
>>> Does this make it less atomic? No. The assembler instruction is just
>>> as atomic as it was before. This is all that matters.
But what about the additional stack manipulations involved in a function
call ? I agree that things have to be done the way they are, and that
advantage has to be taken of the processors equivalent of a TSL
instruction.
next reply other threads:[~1999-06-19 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-19 15:52 pip [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-19 11:52 forsyth
1999-06-19 9:20 Nigel
1999-06-18 16:55 pip
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=19990619155202.vobGUQCd-FWL1YqAHi4GraMGao-E7B28nfqXMg_tD8A@z \
--to=9fans@9fans.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 NNTP newsgroup(s).