@stephentyrone @whitequark @FioraAeterna Yes, but that requires adding fenv to softfloat.
-
-
Replying to @RichFelker
@RichFelker@whitequark@FioraAeterna That's *a* solution, not the only solution.2 replies 0 retweets 1 like -
Replying to @stephentyrone
@stephentyrone@whitequark@FioraAeterna From a standpoint of conforming to current standards I think it's the only one.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@whitequark@FioraAeterna From that standpoint we need to continue supporting math-errno. I am uninterested in that world.1 reply 0 retweets 2 likes -
Replying to @stephentyrone
@stephentyrone@whitequark@FioraAeterna No, standards only require either fenv exception flags or errno, not both. errno can be dropped.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@whitequark@FioraAeterna For stdlib implementors. For users and compilers (targeting arbitrary stdlibs), no.1 reply 0 retweets 0 likes -
Replying to @stephentyrone
@RichFelker@whitequark@FioraAeterna while I have a personal interest in life being easy for stdlibs, that's the least value of the three.1 reply 0 retweets 0 likes -
Replying to @stephentyrone
@stephentyrone@whitequark@FioraAeterna For stdlib implementors, supporting softfloat fenv is more work than errno.2 replies 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@whitequark@FioraAeterna I agree, and both are abominations, which is why I want to tear the whole thing down.1 reply 0 retweets 0 likes -
Replying to @stephentyrone
@stephentyrone@whitequark@FioraAeterna For fenv there's a standards-conforming way to say "don't need it":#pragma STDC FENV_ACCESS OFF1 reply 0 retweets 2 likes
@stephentyrone @whitequark @FioraAeterna Then, if the compiler can assume errno is not used, it can hoist ALL math functions at will.
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.