https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106723
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I think better would be to error out (or just warn) if we see a valid mode/code attribute which doesn't handle the corresponding mode/code. For the PR106721, that would diagnose all but the last issue where there was a typo, but that one is hard to distinguish from <x> or <logic> etc. appearing in comments or perhaps assembly syntax on some targets.
