On 2020-03-06 07:48 PM, Robert Armstrong wrote:
Thanks, Olaf, for the updates. macro11 is working pretty well now.
Is there a a path from macro11 .obj files to absolute memory images,
preferably in -11 absolute loader paper tape image format, that I can
transfer to a real -11?
Thanks, Olaf, for the updates. macro11 is working pretty well now.
Is there a a path from macro11 .obj files to absolute memory images, preferably
in -11 absolute loader paper tape image format, that I can transfer to a real
-11?
Did someone say that there’s link11 as well? Or a task
On 2020-03-06 04:59 PM, Johnny Billquist wrote:
On 2020-03-07 01:52, Don North wrote:
On 2020-03-06 02:53 PM, Robert Armstrong wrote:
Another macro11 question - do the apostrophes in the listing indicate
relocatable references, as they do in the DEC version?
If so, then I don't think
> .ENABL AMA ...
Ah, you are right - it's generating mode 67 rather than 37.
.ENABL AMA does fix that issue. Thanks!
Bob
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
On 2020-03-07 01:52, Don North wrote:
On 2020-03-06 02:53 PM, Robert Armstrong wrote:
Another macro11 question - do the apostrophes in the listing indicate
relocatable references, as they do in the DEC version?
If so, then I don't think it's assembling this code correctly -
1
On 2020-03-06 02:53 PM, Robert Armstrong wrote:
Another macro11 question - do the apostrophes in the listing indicate
relocatable references, as they do in the DEC version?
If so, then I don't think it's assembling this code correctly -
1
> On Mar 6, 2020, at 5:53 PM, Robert Armstrong wrote:
>
>
> Another macro11 question - do the apostrophes in the listing indicate
> relocatable references, as they do in the DEC version?
>
> If so, then I don't think it's assembling this code correctly -
>
>
> 1
Another macro11 question - do the apostrophes in the listing indicate
relocatable references, as they do in the DEC version?
If so, then I don't think it's assembling this code correctly -
1.TITLE TEST RELOCATABLE
REFERENCES
2 00
On Wed 04 Mar 2020 at 15:36:02 -0700, Kevin Handy wrote:
> Not sure.
Since I'm not sure either, I'll just leave it alone. Maybe somebody else
has an idea at some point.
-Olaf.
--
Olaf 'Rhialto' Seibert -- rhialto at falu dot nl
___ Anyone who is capable of getting themselves made President
There are a lot of missing features in this macro11 already that are
handled as no-ops, mostly regarding the listing. To do this properly would
require implementing much of the missing listing functionality like paging,
page titles, etc.
I think the first step is to make it not fail on existing
> On Mar 6, 2020, at 4:16 PM, Rhialto wrote:
>
> On Fri 06 Mar 2020 at 08:18:07 -0800, Robert Armstrong wrote:
>> macro11 will assemble this once (or try to, without much success)
>> anyway, despite the ?0?. Is there a reason for this, or is this
>> just a bug?
>
> I guess it's a bug. The
On Fri 06 Mar 2020 at 08:18:07 -0800, Robert Armstrong wrote:
> macro11 will assemble this once (or try to, without much success)
> anyway, despite the ?0?. Is there a reason for this, or is this
> just a bug?
I guess it's a bug. The code in rept_irpc.c line 44 seems to decrement
and check
On Thu 05 Mar 2020 at 17:10:29 -0700, Kevin Handy wrote:
> A quick fix to make PAGE a no-op, would be to add a line in assemble.c
> right after the line
>case P_PRINT:
> and add the line
>case P_PAGE:
>
> I don't think that much of the listing ops really work anyway.
Indeed. And the
I’ve been reading this conversation about macro11 and decided to try running
a few old source files thru it. One problem I’ve noticed right away is that
“.REPT 0” doesn’t seem to work as it did it the official DEC assemblers. A lot
of code will do something like
.REPT
14 matches
Mail list logo
