Conversation

Notices

1. Embed this notice
   [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic: (novenary@akko.wtf)'s status on Wednesday, 06-Nov-2024 21:15:32 JST [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic:
   what tool could change a static library's object order?
   • Embed this notice
     [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic: (novenary@akko.wtf)'s status on Wednesday, 06-Nov-2024 21:15:30 JST [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic:

     in reply to
     and I can't just go ask them wtf is going on :/
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic: (novenary@akko.wtf)'s status on Wednesday, 06-Nov-2024 21:15:31 JST [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic:

     in reply to
     it's pretty inconsequential other than it messing with code ordering in the final binary, which hurts reproducibility between the packaged toolchain and one built from source
   • Embed this notice
     [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic: (novenary@akko.wtf)'s status on Wednesday, 06-Nov-2024 21:15:32 JST [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic:

     in reply to
     devkitpro seems to be doing *something* to newlib because my builds from source have a predictable order that matches the makefile exactly
     but their packaged binaries have a completely different object order and I have no idea where that's coming from