On Oct 30, 2014, at 10:25 AM, Andrew Stubbs <a...@codesourcery.com> wrote: > Many of the tests in gcc.target/powerpc specify an explicit -mcpu option with > dg-options.
So, I think this isn’t the strategy people like for this sort of thing. The problem is default flags. You can have a certain cpu as a target but no flag for it, no flag, no way to skip based upon that flag. > Also, I'm fairly dissatisfied with the current situation where a test uses > dg-require-effective-target to test the default target, and then adds options > that would change the result of that test; it can cause a test to get skipped > when actually it would work fine. Anyway, that's a problem for a different > day. But, that code works the way you want it to? If you don’t want to add a flag, you don’t.
