On Wed, Sep 14, 2016 at 7:27 AM, Klemens Krause <
kra...@informatik.uni-stuttgart.de> wrote:
>
> I found the next simplification:
>
> BSWI, 0
>DCA SAVEAC
>RTR / MOVE LINK TO THE PREROTATE POSITION
>RTR / ELIMINATE C0100
>RTR / LINK IS CLEARE
On 14/09/2016 17:02, Vincent Slyngstad wrote:
From: Pete Turnbull: Wednesday, September 14, 2016 7:20 AM
ISZ ovfsum/ if yes, 3777 -> 4000 (MIN INT) CLA
/ really a NOP
You should be able to remove the CLA, as that ISZ won't skip
Of course! LOL! I must have spent half an hour looking
From: Pete Turnbull: Wednesday, September 14, 2016 7:20 AM
ISZ ovfsum/ if yes, 3777 -> 4000 (MIN INT)
CLA / really a NOP
You should be able to remove the CLA, as that ISZ won't skip
and the AC is already clear.
Yours is definitely better, I think, as the XOR business di
On 14/09/2016 13:17, Vincent Slyngstad wrote:
From: Kyle Owen: Tuesday, September 13, 2016 7:12 PM
TAD OVFA /A XOR B
AND OVFB
CMA IAC
TAD OVFA
TAD OVFB
Sigh.
There seems to be an issue with my implementation of XOR.
Before the CMA IAC there needs to be CLL RAL, to reposition the carries
befor
On 14/09/2016 03:12, Kyle Owen wrote:
Need some more optimization fun? :) Vince and I were working on some code
to add two signed 12 bit numbers and detect overflow, returning MAX_INT or
MIN_INT in AC in the case of overflow, or the sum in AC otherwise. Here's
what Vince came up with so far:
>
>
On Tue, 13 Sep 2016, Doug Ingraham wrote:
Not bad but I realized even more was possible.
31 00210 BSWI, .-. /ENTRY POINT
32 00211 3174 DCA SAVEAC
33 00212 7430 SZL /REMEMBER LINK STATE
34 00213 1176 TAD C0100 /PRE RO
From: Kyle Owen: Tuesday, September 13, 2016 7:12 PM
TAD OVFA /A XOR B
AND OVFB
CMA IAC
TAD OVFA
TAD OVFB
Sigh.
There seems to be an issue with my implementation of XOR.
Before the CMA IAC there needs to be CLL RAL, to reposition
the carries before subtracting them. Both XORs are affected.
On Tue, Sep 13, 2016 at 7:16 PM, Vincent Slyngstad wrote:
> From: Vincent Slyngstad: Tuesday, September 13, 2016 6:00 PM
>
>> Poof! There goes the prior value of link! And the "0" in the comment is
>> correct.
>>
>
> Never mind. I finally see what Klemens and others were trying to tell me
> ab
On Tue, Sep 13, 2016 at 3:38 PM, Doug Ingraham
wrote:
>
> Thanks for an interesting bit of optimization!
Need some more optimization fun? :) Vince and I were working on some code
to add two signed 12 bit numbers and detect overflow, returning MAX_INT or
MIN_INT in AC in the case of overflow, or
From: Vincent Slyngstad: Tuesday, September 13, 2016 6:00 PM
Poof! There goes the prior value of link! And the "0" in the comment
is correct.
Never mind. I finally see what Klemens and others were trying to tell me
about the need for CLL.
Vince
From: Doug Ingraham: Tuesday, September 13, 2016 1:38 PM
This struck me as a pretty clever bit of code. My first cut used 23 words
including 2 masks and 3 temporaries.
Thanks!!
This is the working version of Vince's original. It uses 18 words
including 1 mask and 2 temporaries.
I have done
On Tue, Sep 13, 2016 at 2:55 PM, Klemens Krause <
kra...@informatik.uni-stuttgart.de> wrote:
>
> First PAL8 complained about "IFNZER". PAL8 wants "IFNZRO"!
> After changing this, assambly was successfull, and I could start the
> program on the straight-8. All seemed to be ok, with the exception,
>
Vince,
This struck me as a pretty clever bit of code. My first cut used 23 words
including 2 masks and 3 temporaries.
This is the working version of Vince's original. It uses 18 words
including 1 mask and 2 temporaries.
I have done some edge testing and it appears to work.
30 /
On Tue, Sep 13, 2016 at 1:55 PM, Klemens Krause
wrote:
> Next question: my hp35 has 36 keys. The 36th key is not accessible
> for normal users. It's hidden below the "ENTER" key. What does this
> key do? If I remember right, it's a kind of debug-key. I believe it
> shifts the whole register includ
On Wed, 7 Sep 2016, Kyle Owen wrote:
Glad some folks got a kick out of it enough to try it out! Feel free to
suggest improvements where you see fit. I was thinking about adding support
to read keystrokes from a file for macro programmability...but that might
be too absurd even for this project.
Just pushed the changes; please give it a try! Printing terminal support is
next, then maybe I'll tackle the HP-45 error display.
Thanks!
Kyle
On Fri, Sep 9, 2016 at 10:07 AM, Klemens Krause <
kra...@informatik.uni-stuttgart.de> wrote:
>
> I tried both versions with the emulator, and both gave identical
> results. So I tested another "BSW"-replacement, simply:
> BSWEMU,
> RTR
> RTR
> RTR
> JMP I BSWEMU
On Thu, 8 Sep 2016, Vincent Slyngstad wrote:
From: Kyle Owen: Thursday, September 08, 2016 5:43 PM
On Sep 8, 2016 8:28 PM, "Vincent Slyngstad" wrote:
That should probably be:
7 00402 7620 snl cla / Link set?
8 00403 7140 cll cma / No, remember it
Needs more
From: Kyle Owen: Thursday, September 08, 2016 5:43 PM
On Sep 8, 2016 8:28 PM, "Vincent Slyngstad" wrote:
That should probably be:
7 00402 7620 snl cla / Link set?
8 00403 7140 cll cma / No, remember it
Needs more testing :-/.
Probably can make it "snl" inst
On Sep 8, 2016 8:28 PM, "Vincent Slyngstad"
wrote:
>
> From: "Vincent Slyngstad"
> Sent: Thursday, September 08, 2016 5:07 PM
>
>> 7 00402 7630 szl cla / Link set?
>> 8 00403 7140 cll cma / Yes, remember it
>
>
> That should probably be:
> 7 00402 7620
On Sep 8, 2016 8:07 PM, "Vincent Slyngstad"
wrote:
>
> Here's my slightly optimized version, for what it's worth:
Nice work. Definitely shorter than mine. I was just working on an
optimization that used ISZ, but you beat me to it!
>
> Some assemblers flag the "(" construct when used on page 0, B
From: "Vincent Slyngstad"
Sent: Thursday, September 08, 2016 5:07 PM
7 00402 7630 szl cla / Link set?
8 00403 7140 cll cma / Yes, remember it
That should probably be:
7 00402 7620 snl cla / Link set?
8 00403 7140 cll cma /
From: Kyle Owen: Thursday, September 08, 2016 3:53 PM
How does the following compare to your BSWEMU, by the way? This ensures
that the link bit remains untouched, which may or may not be important in
every case of BSW in my application.
I'm sure I've seen some code before that does this, but I
On Thu, Sep 8, 2016 at 8:30 AM, Klemens Krause <
kra...@informatik.uni-stuttgart.de> wrote:
>
> I tried it out: I dowloaded the hp35only.pal-source, because it needs only
> 4K of memory, kermited it to my PDP8/E and succeeded assembling with PAL8
> without modifying the PALBERT-code.
> After starti
On Wed, 7 Sep 2016, Kyle Owen wrote:
I updated the project to include optional OS/8 support. I won't say I've
tested it extensively, but it does seem to be working as expected in SimH,
anyways. I updated the README to reflect the additions.
...
I tried it out: I dowloaded the hp35only.pal-sou
09:53 AM
Subject: Re: HP-35/45 Simulator for PDP-8
I'd vote for the HP-1xC line myself. You can get 5 different calculators
(financial, 3 x scientific and programmer) for nearly the effort of the
first one.
The HP-16C (http://www.hpmuseum.org/hp16.htm) would be especially helpful
as it c
09:53 AM
Subject: Re: HP-35/45 Simulator for PDP-8
I'd vote for the HP-1xC line myself. You can get 5 different calculators
(financial, 3 x scientific and programmer) for nearly the effort of the
first one.
The HP-16C (http://www.hpmuseum.org/hp16.htm) would be especially helpful
as it c
On Wed, Sep 7, 2016 at 9:15 AM, Kyle Owen wrote:
> I could imagine OS/8 would come in handy here, as we could swap fields out,
> maybe between several fields of ROM instructions, as kind of a cache
> approach. There would be a ROM file that's required for use.
I thought about swapping, but the mi
I'd vote for the HP-1xC line myself. You can get 5 different calculators
(financial, 3 x scientific and programmer) for nearly the effort of the
first one.
The HP-16C (http://www.hpmuseum.org/hp16.htm) would be especially helpful
as it can easily be converted to calculate with a 12 bit with carry
On Sep 7, 2016 6:27 AM, "Eric Smith" wrote:
>
> On Wed, Sep 7, 2016 at 12:10 AM, Kyle Owen wrote:
> > Maybe the HP-41C simulator is next...
>
> That will definitely be entertaining.
>
> It will need three PDP-8 fields just for the 41C ROMs (12Kx10), and
> 400 words for the basic 41C RAM (16 "stat
On Wed, Sep 7, 2016 at 12:10 AM, Kyle Owen wrote:
> Maybe the HP-41C simulator is next...
That will definitely be entertaining.
It will need three PDP-8 fields just for the 41C ROMs (12Kx10), and
400 words for the basic 41C RAM (16 "status" registers, 64
data/program registers, all of 56 bits ea
I updated the project to include optional OS/8 support. I won't say I've
tested it extensively, but it does seem to be working as expected in SimH,
anyways. I updated the README to reflect the additions. The directory
structure was also updated to something more sane.
The keen observer will note t
On Sun, Sep 04, 2016 at 10:43:19PM -0700, Mark J. Blair wrote:
>
> > On Sep 4, 2016, at 21:39, Kyle Owen wrote:
> >
> > Just thought I'd share with you all one of my pet projects for the past few
> > years. I have written an HP-35 and HP-45 simulator for the PDP-8, which
> > uses the original mi
> On Sep 4, 2016, at 21:39, Kyle Owen wrote:
>
> Just thought I'd share with you all one of my pet projects for the past few
> years. I have written an HP-35 and HP-45 simulator for the PDP-8, which
> uses the original microcode from these calculators. Thus, it is just as
> accurate as the origi
Just thought I'd share with you all one of my pet projects for the past few
years. I have written an HP-35 and HP-45 simulator for the PDP-8, which
uses the original microcode from these calculators. Thus, it is just as
accurate as the original calculators, I would believe.
Not really sure why I d
35 matches
Mail list logo
