https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123286
XChy <xxs_chy at outlook dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xxs_chy at outlook dot com
--- Comment #4 from XChy <xxs_chy at outlook dot com> ---
(In reply to Andrew Pinski from comment #2)
> I am going to implement this for GCC 17. Note might cause some fuzzers NOT
> to run into things as much as right now they are abusing we don't simplify
> at the gimple level to find issues on the RTL level :).
Yes, our fuzzer relies on this feature to resist middle-end canonicalization,
so it can detect backend issues. Just out of curiosity, is there any stable
middle-end optimization barrier that only folds in the backends in GCC, like
vqadd_u64(x, 0)? And how do you think of testing with such barriers?
