On Mon, Dec 19, 2016 at 06:00:21PM +0100, Jakub Jelinek wrote: > On Mon, Dec 19, 2016 at 05:50:40PM +0100, Dominik Vogt wrote: > > * config/s390/s390-c.c (s390_cpu_cpp_builtins_internal): Define > > __S390_ARCH_LEVEL__. > > gcc/testsuite/ChangeLog-setmem > > > > * gcc.target/s390/md/setmem_long-1.c: Use "runnable". > > * gcc.target/s390/md/rXsbg_mode_sXl.c: Likewise. > > * gcc.target/s390/md/andc-splitter-1.c: Likewise. > > * gcc.target/s390/md/andc-splitter-2.c: Likewise. > > * lib/gcc-dg.exp (gcc-dg-runtest): Export torture_current_flags. > > * gcc.target/s390/s390.exp: Import torture_current_flags. > > (check_effective_target_runnable): New. > > Unless you want to add support for all targets in the runnable > effective target, I think it would be better to call it less generically, > s390_runnable or similar.
Fair enough. What do you think about the change in gcc-dg.exp? We couldn't decide whether it's a valid way of retrieving the flags needed for compiling s390_check_runnable or not. It would be nice to get all options that are relevant for the test case, including the ones from "dg-options" (etc.), but that probably requires larger changes to lib/*.exp. (The target specific check functions could be removed then.) Ciao Dominik ^_^ ^_^ -- Dominik Vogt IBM Germany
