On Mon, 27 Apr 2020 at 22:58, Mike Stump <mikest...@comcast.net> wrote: > > On Apr 27, 2020, at 12:43 PM, Christophe Lyon via Gcc-patches > <gcc-patches@gcc.gnu.org> wrote: > > It seems it's not possible to write these tests so that they works in > > all combinations of toolchain configuration and options used for testing :-( > > So, generally, you can have each change in configuration reflected in a > preprocessor symbol and each command line change also reflected. Then, in > the test case you merely interrogate all the state as necessary to decide. > If that weren't enough, then, we'd have some other mechanism that we could > interrogate with if, and then you'd be off and running. > > [ ducks ] > > Think > > if (__builtin_arm_have_featurea()) > // test case for featurea. > else ... > > I can appreciate if the support necessary for the if or the #ifdef is > missing, but, it could be added.
I'm not sure to understand: the dg-require-effective-targets check flag combinations independently of each other, but in this case they are not independent.
