aboutsummaryrefslogtreecommitdiff
path: root/gcc/fortran/trans-expr.c
diff options
context:
space:
mode:
authorHans-Peter Nilsson <hp@bitrange.com>2020-08-09 04:33:34 +0200
committerHans-Peter Nilsson <hp@bitrange.com>2020-08-09 04:33:34 +0200
commitfb9e3f7946440e513e897aa2ce45ddd1001d5871 (patch)
tree52f3d81229e1c4f125ba022ec66e9beb09b0507f /gcc/fortran/trans-expr.c
parentbc0ca715c2968b0b09ce170adc9ab0b88b2a3922 (diff)
downloadgcc-fb9e3f7946440e513e897aa2ce45ddd1001d5871.zip
gcc-fb9e3f7946440e513e897aa2ce45ddd1001d5871.tar.gz
gcc-fb9e3f7946440e513e897aa2ce45ddd1001d5871.tar.bz2
gcc.dg/pr44194-1.c: Skip for mmix.
The test makes sense only for targets that return the "struct { int a, b, c; }" in registers (not in memory). Starting a skip-construct is IMHO better than another iteration of that obscuring "{ ... && { ! mytarget-*-* } }". New targets can just append to the list without additional {}:s. I chose not to "convert" any of the previous exclusions, as without targets to test, I'd surely mess up {}-pairs. A new effective_target would be even better, but such a check_effective_target_returns_struct_in_memory (or complementary, _in_registers) would surely have to be parametrized on the size and type of the returned blob. Maybe best to restrict to just x86_64, as seems to have been the original problem target. gcc/testsuite: * gcc.dg/pr44194-1.c: Skip for mmix.
Diffstat (limited to 'gcc/fortran/trans-expr.c')
0 files changed, 0 insertions, 0 deletions