Uhg, gcc is doing the idiotic llvm thing of maximally-hoisting large stack usage, and also float usage (saving call-saved float regs). This surprisingly leads to hardfloat code SIGILL'ing on nofpu machines even when the float code is never reached.
-
-
-
Replying to @cooljeanius
It's not strictly a "bug", but a QoI issue that can cause code that "should" work at a given stack size to stack overflow, and that hurts performance in some code paths.
1 reply 0 retweets 1 like -
Replying to @RichFelker @cooljeanius
I think it's known that gcc shrinkwraps poorly, but I'm not sure if I found new things that aren't already known.
2 replies 0 retweets 1 like -
Replying to @RichFelker @cooljeanius
Would you prefer a user to not bring up an issue they have with musl when they are unsure whether it's already known? Would you prefer them not bring it up when they are sure it was known, but was last discussed couple of years back as far as they know?
1 reply 0 retweets 1 like -
Replying to @_monoid @cooljeanius
No, I'm looking into it before posting though.
1 reply 0 retweets 1 like
I want to construct a minimal mips example that saves and restores fpu regs in a non-float code path.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.