From: Thomas Koenig <tkoenig@netcologne.de>
To: Sandra Loosemore <sandra@codesourcery.com>,
Thomas Schwinge <thomas@codesourcery.com>,
gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Pushing XFAILed test cases
Date: Sat, 17 Jul 2021 09:25:33 +0200 [thread overview]
Message-ID: <a4fbe2f9-1068-4f31-05bb-bb987b6c31a6@netcologne.de> (raw)
In-Reply-To: <18f90084-4d3a-f6f0-8a2a-d305ce152b0d@codesourcery.com>
On 16.07.21 20:22, Sandra Loosemore wrote:
> So it seems to me rather surprising to take the position that we should
> not be committing any new test cases that need to be XFAILed
It is what I was told in no uncertain terms some years ago, which
is where my current state of knowledge comes from.
So, I have added the gcc mailing list to this discussion, with a
general question.
Is it or is it not gcc policy to push a large number of test cases
that currently do not work and XFAIL them?
Regards
Thomas
next prev parent reply other threads:[~2021-07-17 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 3:46 [PATCH, Fortran] Bind(c): CFI_signed_char is not a Fortran character type Sandra Loosemore
2021-07-16 7:52 ` Thomas Koenig
2021-07-16 15:32 ` Pushing XFAILed test cases (was: [PATCH, Fortran] Bind(c): CFI_signed_char is not a Fortran character type) Thomas Schwinge
2021-07-16 17:26 ` Pushing XFAILed test cases Martin Sebor
2021-07-16 18:22 ` Sandra Loosemore
2021-07-17 7:25 ` Thomas Koenig [this message]
2021-07-21 9:20 ` Tobias Burnus
2021-07-22 8:03 ` [PATCH, Fortran] Bind(c): CFI_signed_char is not a Fortran character type Tobias Burnus
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=a4fbe2f9-1068-4f31-05bb-bb987b6c31a6@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=sandra@codesourcery.com \
--cc=thomas@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).