Re: DSPSERV CREATE, is ORIGIN parm a relic?

2020-03-07 Thread Mike Hochee
: DSPSERV CREATE, is ORIGIN parm a relic? Caution! This message was sent from outside your organization. ZAD is to deal with base registers (register 0 can never be a base register) loaded with 0 being incorrectly used to read data in the first 4k by instructions with a base/12-bit displacement. While

Re: DSPSERV CREATE, is ORIGIN parm a relic?

2020-03-07 Thread Binyamin Dissen
On Fri, 6 Mar 2020 16:01:41 -0600 Michael Hochee wrote: :>Ideally, I would like to create all future data spaces with a size of 2GB, rather than 2GB OR 2GB-4K (when the returned ORIGIN value is NZ). I looked at assembler service reference manuals as far back as 1999, and they all state that

Re: DSPSERV CREATE, is ORIGIN parm a relic?

2020-03-07 Thread Don Poitras
ZAD is to deal with base registers (register 0 can never be a base register) loaded with 0 being incorrectly used to read data in the first 4k by instructions with a base/12-bit displacement. While long-displacement instructions could incorrectly read data in the first 512K of a dataspace, I

Re: DSPSERV CREATE, is ORIGIN parm a relic?

2020-03-07 Thread Mike Schwab
With 64 bit machines, each processor now has 8K unique to it. Do they need to avoid the first 8K? On Sat, Mar 7, 2020 at 7:25 AM Peter Relson wrote: > > Answer: Not totally > > It is true that all current machines support page 0 in a data space, and > for them the "normal" origin returned would

Re: DSPSERV CREATE, is ORIGIN parm a relic?

2020-03-07 Thread Peter Relson
Answer: Not totally It is true that all current machines support page 0 in a data space, and for them the "normal" origin returned would be 0. That is not a guarantee that all future machines would have such support, but I find it hard to believe any would not. However, we have found it highly