From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Why Plan 9 C compilers don't have asm("")
Date: 6 Jul 2001 17:16:57 -0700 [thread overview]
Message-ID: <9i5kdp$qvs$1@cesium.transmeta.com> (raw)
In-Reply-To: <200107061724.NAA14777@smarty.smart.net> <15174.20383.84051.790269@pizda.ninka.net>
Followup to: <15174.20383.84051.790269@pizda.ninka.net>
By author: "David S. Miller" <davem@redhat.com>
In newsgroup: linux.dev.kernel
>
> Rick Hohensee writes:
> > Forth chips aren't modern in the true-multi-user sense, but if an
> > individual were to design such a beast they could get several of them,
> > hundreds maybe, on FPGAs available now. Such things are coming, because a
> > Forth chip IS something an individual can design.
>
> And I suppose this zero-cost call is also handling things like keeping
> an N stage deep pipeline full during this call right?
>
Believe it or not, that's actually a fairly simple part of the whole
machinery. All you need for that is to maintain a call/return stack
in the front end of the pipe. That way, a return that is indeed a
return can be speculated properly; obviously, if the speculation
doesn't work out when you get the return address in the execution
stage you suffer a branch mispredict penalty.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-07-07 0:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 17:24 Why Plan 9 C compilers don't have asm("") Rick Hohensee
2001-07-06 23:54 ` David S. Miller
2001-07-07 0:16 ` H. Peter Anvin [this message]
2001-07-07 0:37 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 4:39 Rick Hohensee
2001-07-09 3:03 Rick Hohensee
[not found] <mailman.994629840.17424.linux-kernel2news@redhat.com>
2001-07-09 0:08 ` Pete Zaitcev
2001-07-09 0:28 ` Victor Yodaiken
2001-07-07 6:16 Rick Hohensee
2001-07-05 3:26 Rick Hohensee
2001-07-04 10:10 Rick Hohensee
2001-07-04 3:37 Rick Hohensee
2001-07-04 3:36 ` Olivier Galibert
2001-07-04 6:24 ` Cort Dougan
2001-07-04 8:03 ` H. Peter Anvin
2001-07-04 17:22 ` Linus Torvalds
2001-07-06 8:38 ` Cort Dougan
2001-07-06 11:43 ` David S. Miller
2001-07-06 18:44 ` Linus Torvalds
2001-07-06 20:02 ` Cort Dougan
2001-07-08 21:55 ` Victor Yodaiken
2001-07-08 22:28 ` Alan Cox
2001-07-08 22:29 ` David S. Miller
2001-07-09 1:22 ` Johan Kullstam
2001-07-21 22:10 ` Richard Henderson
2001-07-22 3:43 ` Linus Torvalds
2001-07-22 3:59 ` Mike Castle
2001-07-22 6:49 ` Richard Henderson
2001-07-22 7:44 ` Linus Torvalds
2001-07-22 15:53 ` Richard Henderson
2001-07-22 19:08 ` Linus Torvalds
2001-07-04 7:15 ` pazke
2001-07-05 1:02 ` Michael Meissner
2001-07-05 1:54 ` Rick Hohensee
2001-07-05 16:54 ` Michael Meissner
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='9i5kdp$qvs$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.