https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88732
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Amos Wang from comment #2) > (In reply to Marc Glisse from comment #1) > > Why not read the documentation for that function? > > "If x is 0, the result is undefined." > > Why the results are different at different optimizing optionss? If it's an > undefined behaviour, I think all results should be the same. undefined behavior means that the value could be different at different times.
