Article View: comp.arch
Article #119Re: What's wrong with stack machines?
From: Nick Janow
Date: Sun, 01 Nov 1992 02:18
Date: Sun, 01 Nov 1992 02:18
20 lines
1240 bytes
1240 bytes
wscott@en.ecn.purdue.edu (Wayne H Scott) writes: > I many disadvantage of a stack machine is directly due to the fact that > all operations work with the same set of arguments. > > You can hardly write two instructions that do not have a data dependance. > Try pipelining a stack machine or a super-scalar. Take a look at some of the modern stack processors (RTX, SC32). There's no pipelining; it's not needed. They do multiple operations per clock cycle by having multiple data paths. One instruction can affect the data stack, the return stack, memory, and I'd have to dig out my data sheets to find out what else. The RTX can do five operation in one clock cycle. You have to consider stack machines according to their own strengths, not how well or not well they handle non-stack language programming techniques. -- Nick_Janow@mindlink.bc.ca
Technical Details
Message-ID:
<17035@mindlink.bc.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!wupost!spool.mu.edu!agate!rsoft!mindlink!a684Show Full Headers
Complete Article Headers
Newsgroups: comp.arch Path: arc1-ca.pugleaf.net!sparky!uunet!usc!wupost!spool.mu.edu!agate!rsoft!mindlink!a684 From: Nick_Janow@mindlink.bc.ca (Nick Janow) Subject: Re: What's wrong with stack machines? Organization: MIND LINK! - British Columbia, Canada Date: Sun, 1 Nov 1992 02:18:42 GMT Message-ID: <17035@mindlink.bc.ca> Sender: news@deep.rsoft.bc.ca (Usenet) Lines: 20