From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: "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 09:31:15 -0700 [thread overview]
Message-ID: <20211023163115.GA80954@troutmask.apl.washington.edu> (raw)
In-Reply-To: <5fabbaa1-30f6-2781-446e-8816a154c5df@netcologne.de>
On Sat, Oct 23, 2021 at 05:56:46PM +0200, Thomas Koenig wrote:
> Hi Steve,
>
> > libgomp.fortran/async_io_[1,2,3,4,8,9].f90 account for a number
> > of FAILS on x86_64-*-freebsd. Please fix.
>
> I'd try to see what is going on, but I have been unable to boot gcc
> (and thus gfortran) on any of the *BSD machines running on the
> gcc compile farm, and more specifically on gcc303 which is a VM
> running FreeBSD, after spending quite some hours on it.
>
> I have submitted a couple of PRs, but apperenty others (including you)
> have a working toolchain, so the PRs have been left unfixed so far.
>
> Also, bootstrapping on gcc303 is going to be a very long process
> because it's a two-processor machine :-|
>
> So, any idea how to proceed?
>
I saw that you were having problems on the compile
farm with bootstrapping a *BSD gcc. I simply cannot
tell why. It just works on a true FreeBSD system.
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. Now that I look at the
commit date of 2020-05-23 for async_io_9.f90, I know these
tests were passing in the past. I fear a reason Sandra/Tobias
commit has broken things.
--
Steve
next prev parent reply other threads:[~2021-10-23 16:31 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 [this message]
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
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=20211023163115.GA80954@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--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).