Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #135036
| From | peter <peter.noreply@tin.it> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Special memory access words (was: GNU Forth has a ...) |
| Date | 2026-05-01 10:22 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <20260501102253.00007757@tin.it> (permalink) |
| References | (3 earlier) <10sv81o$ii2l$1@dont-email.me> <10svbcp$ii2l$2@dont-email.me> <20260430155547.000018f1@tin.it> <10t10r1$13p4b$1@dont-email.me> <2026May1.081638@mips.complang.tuwien.ac.at> |
On Fri, 01 May 2026 06:16:38 GMT anton@mips.complang.tuwien.ac.at (Anton Ertl) wrote: > Krishna Myneni <krishna.myneni@ccreweb.org> writes: > >There is a memory > >words proposal that deals with words like UL@ etc. but I'm not sure > >where it is in the pipeline right now. Gforth also uses UL@ for unsigned > >32-bit fetch. kForth uses UL@ and SL@ for unsigned and signed, > >respectively, and we have UW@ and SW@ -- the mnemonic prefix helps me to > >use the correct version, especially given how different Forth systems > >treated W@ as unsigned in some systems and signed in others. > > The current state of the proposal is: > > https://forth-standard.org/proposals/special-memory-access-words?hideDiff#reply-1531 > > The state is that the committee likes the proposal and I have to find > the time to do a reference implementation and tests to complete it, > then it should progress further. > > As for sw@ and uw@, I used to advocate that approach and precomposed > words in general, but once you add byte-order variations, you get a > lot of words; with precomposed words the W set alone would consist of: > > be-sw@ le-sw@ sw@ be-uw@ le-uw@ uw@ be-w! le-w! w! > > compared to > > w@ w! wbe wle w>s > > in the proposal. Moreover, once you add stuff like "w,", you either > need precomposed versions of that, too, or you need to introduce wbe > and wle anyway. > > So eventually I became convinced of the decomposed approach. W@ > produces an zero-extended (unsigned) result in the proposal. Whatever the standard will be I will continue with <w@, <C@ etc They are a great visual help to see the intent. They are used only in the internals of the compilers and decompilers and will compile to just one cpu opcode For the byte order I agree with the proposal be-sw@ looks horrible BR Peter > > - anton
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar
GNU Forth has a floating point floor word, but not floating point ceiling word? Buzz McCool <buzz_mccool@yahoo.com> - 2026-04-23 16:11 -0700
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? dxf <dxforth@gmail.com> - 2026-04-24 11:14 +1000
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Buzz McCool <buzz_mccool@yahoo.com> - 2026-04-24 08:29 -0700
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-27 17:39 -0500
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? peter <peter.noreply@tin.it> - 2026-04-28 13:40 +0200
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? minforth <minforth@gmx.net> - 2026-04-28 14:01 +0200
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-28 19:25 -0500
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? dxf <dxforth@gmail.com> - 2026-04-29 11:20 +1000
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-29 08:30 -0500
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-29 20:15 -0500
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-05-02 15:56 -0500
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? dxf <dxforth@gmail.com> - 2026-04-29 11:47 +1000
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-30 04:40 -0500
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-30 05:37 -0500
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? peter <peter.noreply@tin.it> - 2026-04-30 15:55 +0200
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-30 20:49 -0500
Special memory access words (was: GNU Forth has a ...) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-05-01 06:16 +0000
Re: Special memory access words (was: GNU Forth has a ...) peter <peter.noreply@tin.it> - 2026-05-01 10:22 +0200
Re: Special memory access words (was: GNU Forth has a ...) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-05-01 08:57 +0000
Re: Special memory access words Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-05-01 10:19 -0500
Re: Special memory access words anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-05-01 15:35 +0000
Re: Special memory access words Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-05-01 13:28 -0500
Re: Special memory access words Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-05-01 13:30 -0500
Re: Special memory access words anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-05-02 05:54 +0000
Re: Special memory access words Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-05-02 15:49 -0500
Re: Special memory access words Hans Bezemer <the.beez.speaks@gmail.com> - 2026-05-01 13:28 +0200
Re: GNU Forth has a floating point floor word, but not floating point ceiling word? peter <peter.noreply@tin.it> - 2026-05-01 10:18 +0200
csiph-web