From: Sandra Loosemore <sandra@codesourcery.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Cc: "Tobias Burnus" <tobias@codesourcery.com>,
"José Rui Faustino de Sousa" <jrfsousa@gmail.com>
Subject: [WIP, Fortran] TS 29113 testsuite
Date: Wed, 30 Jun 2021 23:53:14 -0600 [thread overview]
Message-ID: <64135fb4-c218-4026-6166-5018f11ebfe0@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
For the past several months I've been working on developing a set of
tests for the Fortran/C interoperability features added to Fortran via
TS 29113, "Further Interoperability of Fortran with C":
https://wg5-fortran.org/N1901-N1950/N1942.pdf
The goal here is to exercise gfortran's implementation in a more
systematic and complete way, including conformance with error detection
requirements and the like as well as making sure correct programs run
correctly.
I'm posting this as work-in-progress at this time because, well, there
are a lot of bugs in the implementation causing lots of the tests to
fail. :-( I know maintainers don't like patches that deliberately add
FAILs to the test results and the normal practice seems to be to XFAIL
known bugs with references to a PR. Some of the bugs already have PRs
open, but others don't. What I plan to work on next is filing or
updating the PRs with reference to the testcases that demonstrate the
bugs, add the XFAILs, and then resubmit the patch for approval. A few
of these tests also still have some excessively verbose debugging output
enabled which I'll also try to clean up before resubmitting.
I have a trivial patch for one set of failures (incorrect initialization
of version fields) that I'll be posting shortly. A couple of José's
recent not-yet-committed patches also fix some of the bugs I've run
into; I will note those in the corresponding PRs as I work through the list.
-Sandra
[-- Attachment #2: ts29113-testsuite-wip.patch.gz --]
[-- Type: application/gzip, Size: 51644 bytes --]
next reply other threads:[~2021-07-01 5:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 5:53 Sandra Loosemore [this message]
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
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=64135fb4-c218-4026-6166-5018f11ebfe0@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jrfsousa@gmail.com \
--cc=tobias@codesourcery.com \
/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).