http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60128
--- Comment #29 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> ---
> --- Comment #28 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
>> > What we should do is break the test case into two test cases one for
>> > quad16 and
>> > the other for the rest. Then we XFAIL the quad16 one for solaris. I
>> > think we
>>
>> Agreed, that's better than silently exiting a test in certain
>> conditions, making it seem that it works while it actually doesn't.
>
> For the later remark, this can be handled with something such as the following
> patch:
[...]
Works for me, although in the XFAIL case the output in gfortran.sum
looks a bit strange:
XFAIL: gfortran.dg/fmt_en.f90 -O0 output pattern test, is real(16) are not
rou
nded to nearest
, should match no test skipped
I'd try to keep it on a single line. Now the test is ok on
i386-pc-solaris2.9 (XFAILs as expected) and i386-pc-solaris2.11
(everything PASSes).
> Splitting the test along the real kinds is difficult to do, as some platforms
> don't have real(10) (e.g., powerpc). If the test has to be split, I'ld prefer
> to split it along the line 'wrong outputs' (comment 0 and 6)/ 'rounding tests'
> (those failing on solaris).
That's clearly up to the Fortran maintainers to decide.
Thanks.
Rainer
