https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99137
--- Comment #4 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #3) > ice-on-invalid-code is when an error should be reported and instead of that > the compiler crashes. > ice-on-valid-code is when the code should compile without errors (perhaps > with warnings, and not considering warnings promoted to errors) but the > compiler crashes on it instead. Sure, I understand that. ICE is certainly bad, but I did wonder if this is 'ice-on-invalid-code' (should get error diagnostic instead of ICE), or 'ice-on-valid-code' (should accept this code; 'async(1, 2)' evaluates to 'async(2)'). > I have no idea what OpenACC says about this if anything I've filed <https://github.com/OpenACC/openacc-spec/issues/354> "What does 'async(1, 2)' mean?" (only visible to members of OpenACC GitHub). > in OpenMP [...] Thanks, that makes much sense to me.
