I assumed, at first, that it was somehow falling through the infinite loop and accidentally runnning the unreachable function, but it clearly explicitly runs it in the assembler generated...
edit: ah, it's called from __start, which suggests that main is being elided entirely by the optimiser, and somehow 'unreachable' is simply becoming a defacto 'main'
4 Comments
TheElectroness@lemmy.ml · 4 pts · 3y
I assumed, at first, that it was somehow falling through the infinite loop and accidentally runnning the unreachable function, but it clearly explicitly runs it in the assembler generated...
how odd.
edit: ah, it's called from __start, which suggests that main is being elided entirely by the optimiser, and somehow 'unreachable' is simply becoming a defacto 'main'
exohuman@lemmy.dbzer0.com · 1 pts · 3y
I can see the whole loop being optimized away, but how does the method that isn’t being called get called?
duskfall@lemmy.world · 1 pts · 1y
anders@rytter.me · 0 pts · 3y
@yogthos What. That's not possible? 😃