From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Tobias Burnus <burnus@net-b.de>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: libgomp.fortran/async_io_[1,2,3,4,8,9].f90 fail on FreeBSD
Date: Sat, 23 Oct 2021 12:09:27 -0700 [thread overview]
Message-ID: <20211023190927.GA49764@troutmask.apl.washington.edu> (raw)
In-Reply-To: <0c54f11c-c48f-a514-e9d8-9713d4719e98@net-b.de>
On Sat, Oct 23, 2021 at 08:00:44PM +0200, Tobias Burnus wrote:
> Hi Steve,
>
> On 23.10.21 18:31, Steve Kargl via Fortran wrote:
> > Do you know how to run a single libgomp.fortran test? I tried
> > % gmake check-fortran RUNTESTSFLAGS="gomp.exp=async_io.f90"
> >
> > but this runs all the testcases.
>
> First, it should be RUNTESTFLAGS= (test not tests).
Yes, of course, it was a typo,
> I sincerely doubt that our Fortran commits have broken this – they are not
> related to anything like TS29113, BIND(C), polymorphism or assumed-rank. I
> am even skeptical that any OpenMP change could have caused that, given that
> those do not really use OpenMP at all – but only pthreads (which is the
> reason they are in libgomp as OpenMP also depends on threads). Granted, as
> they are compiled with -fopenmp, libgomp is linked in (but should never be
> called, except for library initialization).
>
> Nonetheless, if it used to work and now fails, something must have changed,
> causing the breakage.
>
> If you compile and run the program manually without the DejaGNU, does it
> fail when compiled as is, compiled with -pthreads, compiled with -fopenmp?
>
I have the gfortran.log file, I'll see if I can reduce the log
to determine why things are broken now.
--
Steve
prev parent reply other threads:[~2021-10-23 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 19:43 Steve Kargl
2021-10-23 15:56 ` Thomas Koenig
2021-10-23 16:31 ` Steve Kargl
2021-10-23 18:00 ` Tobias Burnus
2021-10-23 18:13 ` Tobias Burnus
2023-01-17 0:00 ` Gerald Pfeifer
2021-10-23 19:09 ` Steve Kargl [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=20211023190927.GA49764@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--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).