https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109982
--- Comment #14 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Alexander Monakov from comment #13) > David, did you somehow configure CSmith to emit attributes it wouldn't emit > by default? Yes. Flag --compiler-attributes. I went through the list of csmith compiler flags which are switched off by default. --float, --int128, --uint128 were the other ones. I tried those three out and got many runtime differences. So many that I am waiting for the current set of csmith problems I have found to be resolved, before reporting the new set. > Emitting random attributes makes sense for testing > error recovery (gcc shouldn't ICE on nonsensical attribute combinations), > but less so for checking correctness of generated code, as we see here. It's quite possible that flag --compiler-attributes doesn't work all that well, so it was switched off. I am happy to switch it off in future.
