Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #42258
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Mecrisp-Stellaris technology preview |
| Date | 2015-09-29 15:52 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <87h9mcalf2.fsf@jester.gateway.sonic.net> (permalink) |
| References | <mu3305$6fd$1@newsserver.rrzn.uni-hannover.de> |
Matthias Koch <matthias.koch@hot.uni-hannover.de> writes: > If everything is fine, it should look and feel like the mainstream > Mecrisp-Stellaris, but it tracks the three top stack elements and maps > them to registers whenever possible. This sounds really neat! I'd be interested to know how much code improvement results. I also wonder, is it easier to track just 3 elements instead of an arbitrary number of them? And what happens with those registers across function calls, where the called function might want to do something with those stack elements? Thanks.
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Mecrisp-Stellaris technology preview Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-09-25 11:10 +0200
Re: Mecrisp-Stellaris technology preview Paul Rubin <no.email@nospam.invalid> - 2015-09-29 15:52 -0700
Re: Mecrisp-Stellaris technology preview Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-09-30 13:56 +0200
Re: Mecrisp-Stellaris technology preview Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-09-30 19:02 +0200
Re: Mecrisp-Stellaris technology preview Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-10-05 12:04 +0200
Re: Mecrisp-Stellaris technology preview Paul Rubin <no.email@nospam.invalid> - 2015-10-05 09:48 -0700
Re: Mecrisp-Stellaris technology preview Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-10-06 09:38 +0200
csiph-web