From: Tobias Burnus <tobias@codesourcery.com>
To: Christophe Lyon <christophe.lyon.oss@gmail.com>,
Sandra Loosemore <sandra@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"Thomas Koenig" <tkoenig@netcologne.de>,
"José Rui Faustino de Sousa" <jrfsousa@gmail.com>
Subject: Re: [PATCH v3, Fortran] TS 29113 testsuite
Date: Fri, 3 Sep 2021 11:14:12 +0200 [thread overview]
Message-ID: <83695368-5a76-054c-f0ad-fb5c7f1af9d2@codesourcery.com> (raw)
In-Reply-To: <CAKhMtSKXCwC6UduzYPFZQFSfvOJWcfsN6GGS4mV4VbFyBiURSw@mail.gmail.com>
Hi,
On 03.09.21 09:46, Christophe Lyon wrote:
> I'm not quite sure I understand the expected status of this patch: are
> all the "expected" failures tagged as XFAIL?
I think that's the idea.
> If yes, then there's a problem because I see lots of unresolved on
> aarch64/arm
>
> XFAIL: gfortran.dg/c-interop/cf-descriptor-5.f90 -O0 pr92482 (test
> for bogus messages, line 10)
> PASS: gfortran.dg/c-interop/cf-descriptor-5.f90 -O0 (test for
> excess errors)
> UNRESOLVED: gfortran.dg/c-interop/cf-descriptor-5.f90 -O0
> compilation failed to produce executable
I think that's the usual result for 'dg-do run' tests if the compilation
failed (be it due to errors or due to effective-target-*).
* * *
If I read https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html
correctly, we should use _Float128 for the following errors
"The _Float128 type is supported on all systems where __float128 is
supported or where long double has the IEEE binary128 format."
Applies to:
> For
> typecodes-array-float128.f90
> FAIL: gfortran.dg/c-interop/typecodes-array-float128.f90 -O0 (test
> for excess errors)
> Excess errors:
> /gcc/testsuite/gfortran.dg/c-interop/typecodes-array-float128-c.c:35:32:
> error: '__float128' undeclared (first use in this function); did you
> mean '_Float128'?
> typecodes-sanity.f90
> FAIL: gfortran.dg/c-interop/typecodes-sanity.f90 -O0 (test for
> excess errors)
> Excess errors:
> /gcc/testsuite/gfortran.dg/c-interop/typecodes-sanity-c.c:41:13:
> error: '__float128' undeclared here (not in a function); did you mean
> '_Float128'?
> typecodes-scalar-float128.f90
> FAIL: gfortran.dg/c-interop/typecodes-scalar-float128.f90 -O0 (test
> for excess errors)
> Excess errors:
> /gcc/testsuite/gfortran.dg/c-interop/typecodes-scalar-float128-c.c:34:32:
> error: '__float128' undeclared (first use in this function); did you
> mean '_Float128'?
* * *
> PR100914.f90
> FAIL: gfortran.dg/PR100914.f90 -O0 (test for excess errors)
> Excess errors:
> /gcc/testsuite/gfortran.dg/PR100914.c:8:10: fatal error: quadmath.h:
> No such file or directory
* * *
On a normal x86-64 system, I get XPASS for:
gfortran.dg/PR100914.f90
gfortran.dg/c-interop/typecodes-array-float128.f90
The ! { dg-do run { xfail { { x86_64*-*-* i?86*-*-* } && longdouble128 } } }
does not help as it just checks whether 'sizeof(long double)==16',
which seemingly passes also on x86-64 with 80bit long double.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2021-09-03 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 5:53 [WIP, " Sandra Loosemore
2021-07-07 3:40 ` [PATCH, " Sandra Loosemore
2021-07-25 19:47 ` [PATCH v2, " Sandra Loosemore
2021-07-27 11:07 ` Tobias Burnus
2021-08-19 17:28 ` [PATCH v3, " Sandra Loosemore
2021-09-03 7:46 ` Christophe Lyon
2021-09-03 9:14 ` Tobias Burnus [this message]
2021-09-03 17:18 ` Sandra Loosemore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83695368-5a76-054c-f0ad-fb5c7f1af9d2@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=christophe.lyon.oss@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jrfsousa@gmail.com \
--cc=sandra@codesourcery.com \
--cc=tkoenig@netcologne.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).