From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
fortran@gcc.gnu.org, Thomas Koenig <tkoenig@netcologne.de>
Subject: Re: libgomp.fortran/async_io_[1,2,3,4,8,9].f90 fail on FreeBSD
Date: Tue, 17 Jan 2023 01:00:25 +0100 (CET) [thread overview]
Message-ID: <2ae10afd-c3f4-5ca9-80d6-4c0e9fad90f8@pfeifer.com> (raw)
In-Reply-To: <a6ff03fd-f846-dedc-83f9-2d532b513fb8@net-b.de>
On Sat, 23 Oct 2021, Tobias Burnus wrote:
> @Gerald: Do you see those issues as well? Or do you have an idea what
> could go wrong?
>
> @Gerald (and unrelated to the topic below): Can you provide more log data
> regarding the failing gfortran.dg tests? (Esp. excess errors but also the
> ICE.)
Apologies, it appears I failed to respond back then.
Is there anything I may be able to help with still? I probably won't be
able to debug/hack this, but if you need some more detailed logs or would
like me to test a patch or run some commands, I certainly can do that.
> On 23.10.21 20:00, Tobias Burnus wrote:
>> On 23.10.21 18:31, Steve Kargl via Fortran wrote:
>>> commit date of 2020-05-23 for async_io_9.f90, I know these
>>> tests were passing in the past.
> If I look at Gerald's results for x86_64-unknown-freebsd12.2 at
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-October/730072.html
> I do not see those async fails.
Cheers,
Gerald
next prev parent reply other threads:[~2023-01-17 0:00 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 [this message]
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=2ae10afd-c3f4-5ca9-80d6-4c0e9fad90f8@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
--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).