https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86416
--- Comment #12 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #11) > because e.g. for x86_64-intelmicemul-linux-gnu offloading the error will not > be emitted. If nvptx or gcn offloading is configured, it will be, for hsa > offloading no idea. Uh, more explicitly: for x86_64-intelmicemul-linux-gnu offloading the error will not be emitted *unless* nvptx or gcn offloading is also configured. That's because for OpenMP libgomp testing we don't cycle through the different offload targets individually (via '-foffload', as done for OpenACC libgomp testing), but compile once, for all offload targets. Each approach has its pros and cons; I'm not yet decided on which is best. (What I am decided on, though, is that it's not ideal that by default OpenMP offloading testing is only testing execution with one offload target, the first configured/available. Again there are different solutions possible to this issue, again each with its pros and cons, and this is, of course a separate discussion.)
