Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.acorn.programmer > #418 > unrolled thread

Building a 26bit module

Back to article view | Back to comp.sys.acorn.programmer

Contents

  Building a 26bit module David Pitt <news@pittdj.co.uk> - 2011-06-12 07:55 +0100
    Re: Building a 26bit module cferris@freeRemoveuk.com.invalid - 2011-06-12 11:42 +0100
      Re: Building a 26bit module David Pitt <news@pittdj.co.uk> - 2011-06-12 12:15 +0100

#418 — Building a 26bit module

So I had this really good idea. In order to avoid the "nan bread" bug,
otherwise known as "Nanny Ogg", that occurs with PipeDream4 running with a
32bit CLib I thought to make a true 26bit only RPCemu environment on the
iMac for PipeDream4 using only the ROM CLib of OS4.04.

The catch is that the supplied EtherRPCEm module is 32bit and requires the
32bit CLib. Source is supplied so it should be possible to compile a 26bit
variant.

The first stage was to attempt to build a 32bit version on the Iyonix using
the latest ROOL Tools (cc5.69). It ran into the sand with :-

cmhg -d h.ModHdr  -throwback  @.cmhg.ModHdr -o @.o.ModHdr 
objasm -throwback -NoCache -depend !Depend -from @.s.intveneer -to
@.o.intveneer
ARM AOF Macro Assembler 3.32 (Acorn Computers Ltd) [20 May 2010]
cc -c -depend !Depend -IC: -throwback -zM -Wp -o @.o.Module @.c.Module 
Norcroft RISC OS ARM C vsn 5.69 [20 Oct 2010]
"c.Module", line 236: Error: undeclared name, inventing 'extern int
Podule_ReadInfo'
c.Module: 0 warnings, 1 error, 0 serious errors
AMU: *** exit (1) ***

AMU: *** '!System.310.Modules.Network.EtherRPCEm' not re-made because of
errors ***

Is Podule support really missing from the ROOL Tools. A look around with
!Locate showed that it had been present in the previous Castle Tools cc5.65.
 

Over to the RiscPC which still has the Castle Tools cc5.65. The build then
completes. To make the 26bit module the makefile just needs the '-apcs 3/26'
switch added and the compile needs to be with a 26bit stubs. The module
built and worked. However the 32bit module flag is still set, it should be
zero. What have I missed.

-- 
David Pitt

[toc] | [next] | [standalone]

#419

In message <mpro.lmo0k20000di002vq.news@pittdj.co.uk>
          David Pitt <news@pittdj.co.uk> wrote:

> So I had this really good idea. In order to avoid the "nan bread" bug,
> otherwise known as "Nanny Ogg", that occurs with PipeDream4 running
> with a 32bit CLib I thought to make a true 26bit only RPCemu
> environment on the iMac for PipeDream4 using only the ROM CLib of
> OS4.04.
> 
[snip]

> Over to the RiscPC which still has the Castle Tools cc5.65. The build
> then completes. To make the 26bit module the makefile just needs the
> '-apcs 3/26' switch added and the compile needs to be with a 26bit
> stubs. The module built and worked. However the 32bit module flag is
> still set, it should be zero. What have I missed.
> 

Perhaps the is 32bit flag is now always set.

Why not use 'StubsG' - this is what it was created for.

I wonder if the 'CLib' call could have extra flag on calling - so
programs could have a choice of action?  Nanny Ogg or not.

-- 
Colin Ferris Cornwall UK

[toc] | [prev] | [next] | [standalone]

#420

cferris@freeRemoveuk.com.invalid, on 12 Jun, wrote:

> In message <mpro.lmo0k20000di002vq.news@pittdj.co.uk>
>           David Pitt <news@pittdj.co.uk> wrote:
> 
> > So I had this really good idea. In order to avoid the "nan bread" bug,
> > otherwise known as "Nanny Ogg", that occurs with PipeDream4 running with
> > a 32bit CLib I thought to make a true 26bit only RPCemu environment on
> > the iMac for PipeDream4 using only the ROM CLib of OS4.04.
> > 
> [snip]
> 
> > Over to the RiscPC which still has the Castle Tools cc5.65. The build
> > then completes. To make the 26bit module the makefile just needs the
> > '-apcs 3/26' switch added and the compile needs to be with a 26bit
> > stubs. The module built and worked. However the 32bit module flag is
> > still set, it should be zero. What have I missed.
> > 
> 
> Perhaps the is 32bit flag is now always set.

It just needed a -26bit flag adding to the CMHGflags list.
 
> Why not use 'StubsG' - this is what it was created for.

I have now used StubsG, some 32bit code was leaking in from somewhere.

Thanks.

-- 
David Pitt

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.acorn.programmer

csiph-web