public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: Andre Vehreschild <vehre@gmx.de>
Cc: GCC-Patches-ML <gcc-patches@gcc.gnu.org>,
	GCC-Fortran-ML <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran, 96418] Fix Test coarray_alloc_comp_4.f08 ICEs
Date: Mon, 17 Jun 2024 21:45:15 +0200	[thread overview]
Message-ID: <7fb96a01-e0cf-425f-bb5f-351df122aa3b@gmx.de> (raw)
In-Reply-To: <20240617095117.096bd158@vepi2>

Hi Andre,

Am 17.06.24 um 09:51 schrieb Andre Vehreschild:
> Regarding your question on the coarray-tests that are not in the
> coarray-directory: These test in most cases test only one method of
> implementing coarrays. I.e., they are either testing just -fcoarray=single or
> -fcoarray=lib -lcaf_single, which are two different approaches. The tests in
> the coarray-directory test all available methods to implement coarrays.  Pushing

ah, that explains it.  I only looked at some of the test sources,
but did not think of looking at caf.exp ...

> all coarray-tests into the coarray-directory will fail a lot of them, because
> the behavior of -fcoarray=single and -fcoarray=lib -lcaf_single is different in
> some corner cases. That's why the coarray-tests in the main gfortran-dir are
> separate.
>
> I do understand why it may be confusing, but I don't see an easy solution. Does
> this answer your question?

Indeed it does!

Thanks,
Harald


      reply	other threads:[~2024-06-17 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 14:12 Andre Vehreschild
2024-06-14  7:22 ` Andre Vehreschild
2024-06-14 19:43   ` Harald Anlauf
2024-06-17  7:51     ` Andre Vehreschild
2024-06-17 19:45       ` Harald Anlauf [this message]

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=7fb96a01-e0cf-425f-bb5f-351df122aa3b@gmx.de \
    --to=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vehre@gmx.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).