From: muta...@gmail.com   
      
   On Tuesday, July 6, 2021 at 12:51:50 PM UTC+10, Branimir Maksimovic wrote:   
      
   > > I'm not concerned about speed on older hardware,   
   > > but if it is the cleanest way of removing *all* traces   
   > > of "INT 80H" from an executable then I am interested.   
      
   > Why you are bothered with int 80h? Why don't you use glibc   
   > then you don't need syscalls directly?   
      
   I have my own competing C library. The easiest thing   
   to do is statically-link it to produce an executable that   
   has no dependencies on glibc. The main problem is   
   the embedded "INT 80H" instructions. I now consider   
   that to be unclean, because it mandates the existence   
   of an interrupt table.   
      
   > Yes with vsyscall you don't need int 80h if that suits you...   
      
   Yes, switching to vsyscall sounds like what I want in   
   order to produce clean executables.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)