From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Jerry DeLisle <jvdelisle@charter.net>
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: 12 PR fixed
Date: Sat, 13 Mar 2021 22:05:48 -0800 [thread overview]
Message-ID: <20210314060548.GA2666@troutmask.apl.washington.edu> (raw)
In-Reply-To: <fe22ba09-9968-e1cd-2133-1358901ed216@charter.net>
On Sat, Mar 13, 2021 at 09:13:53PM -0800, Jerry DeLisle wrote:
> Well, I am seeing the falling upon a closer look. I do not know if related
> to the patch yet. Lets make sure this is fixed.
>
> FAIL: gfortran.dg/pr87907.f90 -O (internal compiler error)
> FAIL: gfortran.dg/pr87907.f90 -O (test for excess errors)
> FAIL: gfortran.dg/pr96013.f90 -O (test for excess errors)
> FAIL: gfortran.dg/pr96025.f90 -O (internal compiler error)
> FAIL: gfortran.dg/pr96025.f90 -O (test for errors, line 5)
> FAIL: gfortran.dg/pr96025.f90 -O (test for excess errors)
On my system,
=== gfortran Summary ===
# of expected passes 56305
# of expected failures 232
# of unsupported tests 109
/home/kargl/gcc/obj/gcc/gfortran version 11.0.1 20210313 (experimental) (GCC)
AFAIK, my tree is up-to-date, but then again, git is a foreign
beast to me. Too bad that the people responsible for the switch
to git throw 15 years of corporate knowledge for little gain.
I see what I can do for a ChangeLog. Some of my patches have
lingered in bugzilla for too long. I don't remember all of
the details.
--
steve
next prev parent reply other threads:[~2021-03-14 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 21:33 Steve Kargl
2021-03-14 4:46 ` Jerry DeLisle
2021-03-14 5:13 ` Jerry DeLisle
2021-03-14 6:05 ` Steve Kargl [this message]
2021-03-14 11:38 ` Tobias Burnus
2021-03-14 12:01 ` Tobias Burnus
2021-03-14 15:22 ` Jerry DeLisle
2021-03-15 22:17 ` Steve Kargl
2021-03-14 16:46 ` 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=20210314060548.GA2666@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=jvdelisle@charter.net \
/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).