http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60236
--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> This patch tries to solve the problem in a more general way.
> I wonder if one of you could try this patch on PowerPC?
Sorry for the late answer, but my G5 was buzzy regtesting. With the patch in
comment 5, tested with
make -k check-gfortran RUNTESTFLAGS="vect.exp=pr32380.f
--target_board=unix'{-m32,-m64}'"
I get
=== gfortran tests ===
Schedule of variations:
unix/-m32
unix/-m64
Running target unix/-m32
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /opt/gcc/work/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /opt/gcc/work/gcc/testsuite/gfortran.dg/vect/vect.exp ...
=== gfortran Summary for unix/-m32 ===
# of expected passes 2
Running target unix/-m64
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /opt/gcc/work/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /opt/gcc/work/gcc/testsuite/gfortran.dg/vect/vect.exp ...
=== gfortran Summary for unix/-m64 ===
# of expected passes 2
=== gfortran Summary ===
# of expected passes 4
/opt/gcc/darwin_buildw/gcc/testsuite/gfortran/../../gfortran version 4.9.0
20140218 (experimental) [trunk revision 207836p2] (GCC)
So the patch is OK for powerpc-apple-darwin9.
