[HN Gopher] Porting the Solana eBPF JIT Compiler to ARM64
       ___________________________________________________________________
        
       Porting the Solana eBPF JIT Compiler to ARM64
        
       Author : ingve
       Score  : 38 points
       Date   : 2022-10-12 12:22 UTC (1 days ago)
        
 (HTM) web link (blog.trailofbits.com)
 (TXT) w3m dump (blog.trailofbits.com)
        
       | roddux wrote:
       | Solana really seems like the most interesting Layer-1 chain
       | outside of Ethereum... lots of cool tech.
        
         | javier123454321 wrote:
         | The real question is, why is anything written in Solana better
         | off being run in a blockchain rather than a 'web2' client
         | server architecture.
        
       | ncmncm wrote:
       | This is not "JiT" by any normal definition. I.e., the eBPF is
       | translated to machine code at registration time, just once, and
       | the resulting machine code executed unsupervised thereafter.
       | There is no hint of runtime analysis of usage, or of progressive
       | optimization. The only thing "in-time" about it is that
       | translation from portable to native representation happens after
       | the program starts up.
        
         | Lichtso wrote:
         | It is true that it would be called AoT in the traditional
         | sense.
         | 
         | However, our requirements are others: Instead of a few programs
         | with many complex functions we have lots of programs with
         | simple functions. Thus, we do the runtime analysis and
         | compilation on a program level, not a function level.
        
           | ncmncm wrote:
           | Note I am not complaining about the tech, just terminology.
           | Everything Trail of Bits does is exemplary.
        
       ___________________________________________________________________
       (page generated 2022-10-13 23:02 UTC)