Posts by mpweiher@mastodon.social
 (DIR) Post #Aodm3kbeURHvZ6O9r6 by mpweiher@mastodon.social
       2024-12-02T16:20:01Z
       
       0 likes, 0 repeats
       
       @mothcompute C was close to the hardware until compiler engineers decided to ignore the writing in the ANSI standard on what undefined behavior means and instead went off and started optimizing off it.
       
 (DIR) Post #AtHgueE4lnRwFGA5XU by mpweiher@mastodon.social
       2025-04-20T06:06:12Z
       
       0 likes, 0 repeats
       
       So golang has a machine-independent assembler.  Which is very cool, and yes, machine instruction sets for modern machines are very similar:  ALU instructions, memory load/store, branches.However, it appears that this machine-independent instruction set is not actually used by the compiler's code generator. Instead it has completely machine-specific backends, with all the extra effort that entails.Anybody know why?
       
 (DIR) Post #AtHgugY08gZnRdV1sG by mpweiher@mastodon.social
       2025-04-20T12:16:42Z
       
       0 likes, 0 repeats
       
       @me_ With that heritage, I would expect the opposite:  that the go compiler *does* use the machine-independent assembler.  If not the ASCII syntax, but the binary representation.But it does not.At least as far as I can tell.As far as I can tell, each of the backends goes directly to the target machine, without the machine-independent assembler.