Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-15 Thread Tobias Fröschle via Ql-Users
Hmm. Are we sure about that? When having a glance at the code, it looked to me as SMSQ/E would not use a1 at all, but rather use BV_RIP(a6) instead for the location of the RI stack (just as QDOS does). Tobias > Am 15.02.2018 um 05:08 schrieb Wolf via Ql-Users : > >

Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-15 Thread pjwitte via Ql-Users
I think the whole thing bears further investigation, as there appears to be doubt about other aspects too. Jan Bredenbeek, for example, suggests that: Call parameters                         Return parameters .. A1                                     A1 Preserved He was going to investigate

Re: [Ql-Users] A polite request

2018-02-15 Thread Marcos Cruz via Ql-Users
En/Je/On 2018-02-14 19:40, Norman Dunbar via Ql-Users escribió / skribis / wrote : > Please, please, please do not "hijack" a thread. Don't reply to a > thread and change the subject to something completely unrelated. I agree. That is important. I support your request. Some times, email users

Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-15 Thread Jan Bredenbeek via Ql-Users
On 15 February 2018 at 11:45, pjwitte via Ql-Users wrote: > Update: > After sribbling down the example above, I decided to "weaponise" it to > test the following three premises: > 1) Is A1 preserved?: JS, Minerva and SMSQ/E all appear to do so > Correct as far as I

Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-15 Thread Tobias.Froeschle--- via Ql-Users
Wolfgang, (For some reason, I only seem to see half of the discussion, so bear with me if I repeat something that was said already) What I meant is that to me it looks like: QA.RESPRI takes _one_ argument, and that is the amount of memory you want to grow the RI stack by in D1. The other

Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-15 Thread Wolfgang Lenerz via Ql-Users
Hi, (Tobias) > Hmm. Are we sure about that? Sorry I'm not sure I understand. Am I sure that, as I said, on SMSQ/E it is not necessary to save the stack pointer in BV_RIP(A6) before calling this vector. Yes, that seems quite clear to me from the code. > When having a glance at the code, it

Re: [Ql-Users] A polite request

2018-02-15 Thread Norman Dunbar via Ql-Users
Evening Per, On 15/02/18 17:42, pjwitte via Ql-Users wrote: For my part, I believe Ive apologised very handsomely for the error of my ways (although any forgiveness still seems to be working its way though my accuser's brain) so I have no more to give on this and require no further

Re: [Ql-Users] A polite request

2018-02-15 Thread pjwitte via Ql-Users
On 15/02/2018 14:32, Marcos Cruz via Ql-Users wrote: En/Je/On 2018-02-14 19:40, Norman Dunbar via Ql-Users escribió / skribis / wrote : Please, please, please do not "hijack" a thread. Don't reply to a thread and change the subject to something completely unrelated. I agree. That is

Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-15 Thread pjwitte via Ql-Users
On 15/02/2018 14:46, Wolfgang Lenerz via Ql-Users wrote: <> Thanks for testing these. How big was the amount of memory requested? Big enough that a shift would occur? Yes. Further tests show that d0 sometimes returns zero (at least two different paths) but usually not, ie it returns with

Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-15 Thread Tobias Fröschle via Ql-Users
Neet to reprase my below statement: > Am 15.02.2018 um 16:26 schrieb Tobias.Froeschle--- via Ql-Users > : > > Wolfgang, > > (For some reason, I only seem to see half of the discussion, so bear with me > if I repeat something that was said already) > > What I meant

Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-15 Thread pjwitte via Ql-Users
On 15/02/2018 18:42, pjwitte via Ql-Users wrote:     move.w qa.resri,d0     moveq #0,d0     jsr (a2)     tst.l d0 Err, that should be move.w qa.resri,a2, but I guess that's pretty obvious. The next bit isnt obvious, but is correct. Per ___