From: muta...@gmail.com   
      
   On Saturday, July 10, 2021 at 9:55:14 AM UTC+10, Joe Monk wrote:   
      
   > > Also during this period, the compiler was retargeted to other nearby   
   machines, particularly the Honeywell 635 and IBM 360/370   
      
   > Here is a quote from an actual user of the compiler you talk about:   
   >   
   > "So basically, the 370 C compiler on the PDP emitted 370 assembler language   
   which we assembled and linked under VM/CMS."   
   >   
   > https://akapugs.blog/2018/05/12/370unixpart2/   
      
   An interesting read, thanks.   
      
   > So, "retarget" in the quote above means it outputs assembler for that   
   platform...   
      
   Ok, and is that a problem?   
      
   Or is it only when the C compiler is actually hosted on the   
   platform that it starts to count?   
      
   And then there is yet another level - just because a compiler   
   can run on a platform doesn't mean that it is good enough   
   to compile itself. The compiler may not even be written in   
   the same language.   
      
   I wish to convert PDOS/86 into huge memory model (still   
   8086), and the only way I can do that is using Watcom C   
   running on a Windows-like environment, like Windows or   
   Freedos+HX, or Unix and cross-compiling.   
      
   It's possible that masm or zortech c etc can run on an 8086   
   and produce the correct huge memory model instructions.   
   I haven't seen their output. I've seen Borland output and it   
   is not suitable. Actually I think Watcom used to run on the   
   8086 too.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)