On Fri, Apr 11, 2025 at 09:34:32AM +0200, Rainer Orth wrote:
> * amd64-pc-solaris2.11, which uses the libquadmath path:
> 
>               === cobol Summary for unix ===
> 
> # of expected passes          2925
> # of unexpected failures      108
> # of expected failures                6
> # of unresolved testcases     72
> 
>   According to Iain, Darwin/x86_64 is similar, though.

Note, while on my WS with glibc 2.35 on x86_64-linux make check-cobol
is clean, in our Fedora 42/43 distro build I'm getting
FAIL: cobol.dg/group1/check_88.cob   -O0  output pattern test
FAIL: cobol.dg/group1/check_88.cob   -O1  output pattern test
FAIL: cobol.dg/group1/check_88.cob   -O2  output pattern test
FAIL: cobol.dg/group1/check_88.cob   -O3 -fomit-frame-pointer -funroll-loops 
-fpeel-loops -ftracer -finline-functions  output pattern test
FAIL: cobol.dg/group1/check_88.cob   -O3 -g  output pattern test
FAIL: cobol.dg/group1/check_88.cob   -Os  output pattern test
FAIL: INSPECT_CONVERTING_TO_figurative_constants.out output file test
FAIL: INSPECT_CONVERTING_TO_figurative_constants.out output file test
FAIL: INSPECT_CONVERTING_TO_figurative_constants.out output file test
FAIL: INSPECT_CONVERTING_TO_figurative_constants.out output file test
FAIL: INSPECT_CONVERTING_TO_figurative_constants.out output file test
FAIL: INSPECT_CONVERTING_TO_figurative_constants.out output file test
(dunno if that is because of newer glibc or what).
Both are likely because of the U+0080 and above characters,
in cobol.log from my WS I see
->

Reply via email to