From: cr88192@gmail.com   
      
   On 8/30/2025 1:22 PM, Stefan Monnier wrote:   
   >> Function pointer consists of a pointer to a blob of memory holding   
   >> a code pointer and typically the callee's GOT pointer.   
   >   
   > Better skip the redirection and make function pointers take up 2 words   
   > (address of the code plus address of the context/environment/GOT), so   
   > there's no dynamic allocation involved.   
   >   
      
   FDPIC typically always uses the normal pointer width, just with more   
   indirection:   
      Load target function pointer from GOT;   
      Save off current GOT pointer to stack;   
      Load code pointer from function pointer;   
      Load GOT pointer from function pointer;   
      Call function;   
      Reload previous GOT pointer.   
      
   It, errm, kinda sucks...   
      
   Seemingly, thus far no FDPIC on RV64 targets (in GCC), but does   
   apparently exist for RV32 No-MMU style targets.   
      
      
   I took a lower overhead approach in my PBO ABI (optional callee side   
   GBR/GP reload), but it lacks any implicit way to implement lambdas.   
      
      
   >   
   >          Stefan   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)