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: [PATCH v2, Fortran] TS 29113 testsuite
Date: Sun, 25 Jul 2021 13:47:24 -0600 [thread overview]
Message-ID: <84cbe3c1-b9db-a4ae-649f-c426448f8bcc@codesourcery.com> (raw)
In-Reply-To: <a44a53bf-9c71-0b40-bbbb-d197fe74d4f1@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
Here is an updated version of my TS29113 testsuite. The last version I
posted became kind of bit-rotten after Tobias's commit "Fortran: Fix
bind(C) character length checks" for PR92842, which changed the wording
of the error message that I'd been catching with dg-bogus in many
places. I've also merged some bug fixes to the test cases (most of
which I'd already posted in conjunction with other patches to fix the
associated library function bugs), and updated all the
ISO_Fortran_binding.h #includes on the theory that I will iron out the
remaining include-path problem with my patch series for PR101305 and get
that committed before some consensus is reached on what to do about this
patch.
With this version I'm now getting 263 XFAILs per multilib on x86. With
the bug fix patches I have already posted that are still awaiting
review/committal, 42 of those go away. And this approved but
not-yet-committed patch from Jose
https://gcc.gnu.org/pipermail/gcc-patches/2021-June/572725.html
fixes 6 more.
Reducing the exact number of XFAILs probably doesn't matter to the
meta-discussion about whether it is OK to commit a pile of tests with so
many things XFAILed, but passing around updated patches like this is
about the only way to keep a working version of the testsuite handy to
anyone besides me who might want to help fix some of these bugs and to
make sure we aren't introducing regressions. :-(
-Sandra
[-- Attachment #2: ts29113-jul25.patch.gz --]
[-- Type: application/gzip, Size: 53553 bytes --]
next prev parent reply other threads:[~2021-07-25 19:47 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 ` Sandra Loosemore [this message]
2021-07-27 11:07 ` [PATCH v2, " 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=84cbe3c1-b9db-a4ae-649f-c426448f8bcc@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).