Conversation

Notices

1. polprog68k (gorplop@pleroma.m68k.church)'s status on Saturday, 15-Feb-2025 05:18:59 JST polprog68k

   in reply to

   • Wolf480pl
   • Piggo :verified_horse:
   • mei
   @wolf480pl @piggo @mei
   >8051
   Best CPU!!!
   
   srsly tho - linux kernel uses some tricks with a pointer to zero in the offset_of macro. But I dont remember if NULL being the same as *(0x0) is just true on most platforms or it's actually the standard
   
   #define offsetof(st, m) \
   ((size_t)&(((st *)0)->m))
   • Wolf480pl (wolf480pl@mstdn.io)'s status on Saturday, 15-Feb-2025 05:19:00 JST Wolf480pl

     in reply to

     • Piggo :verified_horse:
     • mei

     @piggo @mei
     > 8051

     I'm sorry ;_;

   • Wolf480pl (wolf480pl@mstdn.io)'s status on Saturday, 15-Feb-2025 05:19:01 JST Wolf480pl

     in reply to

     • Piggo :verified_horse:
     • mei

     @piggo @mei wait they didn't teach you at uni to always use volatile for stuff that actually has to hit the memory bus?

   • Piggo :verified_horse: (piggo@piggo.space)'s status on Saturday, 15-Feb-2025 05:19:01 JST Piggo :verified_horse:

     in reply to

     • Wolf480pl
     • mei
     @wolf480pl @mei so you need to understand what we programmed in 8051 and arm assembly
   • Piggo :verified_horse: (piggo@piggo.space)'s status on Saturday, 15-Feb-2025 05:19:02 JST Piggo :verified_horse:

     in reply to

     • Wolf480pl
     • mei
     @wolf480pl @mei it's fantastic when a compiler does this cowboy reordering in embedded code that accesses some function registers or whatever and it actually stops working. Everything ends up full of volatile to suppress magic
   • Wolf480pl (wolf480pl@mstdn.io)'s status on Saturday, 15-Feb-2025 05:19:03 JST Wolf480pl

     • mei

     @mei yeah... scary shit isn't it?