From: muta...@gmail.com   
      
   On Friday, July 16, 2021 at 12:36:20 PM UTC+10, anti...@math.uni.wroc.pl wrote:   
      
   > > The linker does indeed need to ensure that no individual   
   > > function is split over a 64k boundary.   
      
   > I am not sure if compilers supported this, but single function   
   > bigger that 64k is valid once you allow more than 64k code.   
   > Compiler can use any mixture of near and far jumps inside.   
      
   I've been thinking more about this.   
      
   If a single function is more than 64k, then, by design, my   
   linker would ensure that that function started on a 64k   
   boundary.   
      
   With such an executable loaded into memory, regardless   
   of the segment shift value, I don't see how the compiler   
   could generate any code which mandated a 4-bit shift.   
      
   The far jumps will necessarily have a segment that needs   
   to be correctly relocated.   
      
   The near jumps will be identically aligned in memory, so   
   will also work.   
      
   Am I missing something?   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)