https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96525
Alan Modra <amodra at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-08-10 Assignee|unassigned at gcc dot gnu.org |amodra at gmail dot com CC|amodra at gcc dot gnu.org | Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #4 from Alan Modra <amodra at gmail dot com> --- Yes, the test needs power10_ok, but *not* power10_hw. Despite being a "run" test with one function cpu=power10, no power10 insns are generated. So the executable could in fact be run (even on a power3). If you make the test power10_hw, then it won't be linked unless of course you have power10 hardware or a simulator. Most people don't. We really do want to at least link the compiler output as it is the link stage that shows up the pr96493 problem. I could make the test { do-do link } but running the test is just that little bit better test of the linker output, and as far as I know there isn't a way of saying "link this but only run on power10".