https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103979
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #3) > I think we shouldn't just follow blindly the docs, but see what e.g. Linux > kernel as heavy user of asm goto with outputs (and I think mostly without > volatile) wants. They will need volatile, at least on powerpc. The reason is they use asm goto now for loading/storing from/to userspace. PR 110420 is another case where asm goto is removed on accident due not to being volatile.
