public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Tobias Burnus <burnus@net-b.de>
Cc: Jerry DeLisle <jvdelisle@charter.net>, gfortran <fortran@gcc.gnu.org>
Subject: Re: 12 PR fixed
Date: Sun, 14 Mar 2021 09:46:56 -0700	[thread overview]
Message-ID: <20210314164656.GA5869@troutmask.apl.washington.edu> (raw)
In-Reply-To: <41ccb8db-cf7c-a49c-c84b-dc475f561dfa@net-b.de>

On Sun, Mar 14, 2021 at 12:38:59PM +0100, Tobias Burnus wrote:
> On 14.03.21 06:13, 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)
> 
> I do see the failure with the new patch applied –

Interesting.  I don't see issues, but then again I don't
do git, so something may have gone south in trying to 
generate a patch.  Probably to be expected when patches
ferment in bugzilla.

91960 2021-03-10, patch not in BZ, tipping point, comment longer than code.
93635 2020-02-10, patch comment #2, does not apply cleanly due to changes
95501 2020-06-03, patch comment #1, 1 line, null ptr check
95502 2020-06-03, patch comment #1, 6 lines, 2 null ptr checks
95710 2020-06-17, patch comment #2, 2 null ptr checks, new error msg
96013 2020-06-30, patch comment #6, 10 lines changed
96025 2020-07-01, patch comment #3, 1 line changed, nullifies a typespec (ts).
97122 2020-09-20, patch comment #1, 2 line changed
99256 2021-02-25, patch comment #1, 8 lines, null ptr, new error msg
99349 2021-02-25, patch comment #1, 2 lines deleted
99351 2021-03-03, patch comemnt #1, adds checks on STAT and ERRMSG in SYNCxxx.
99506 (patch for 91960 fixes this one)

None of the above individual patches should have been difficult to review.
All patches, except 91960, developed against svn r280157, so svn vs git
might be an issue.  All testcases not under git control are hand merged
into gcc/gfortran.dg, so again an opportunity for a screw-up.  Took a few
hours to figure out how to generate the posted diff, so again an opportunity
to FU.

95038 Not in mega patch.  Fixes ICE allowing code to compile.  Code should
      issue an error due to missing IMPORT statement in interface.
95372 Not in mega patch.  Change assert() to null ptr check and error msg.
      Harald has assigned this to himself.  Stopped working on bug.
95613 Not in mega patch.  Removes legacy extension of branching to
      to a label in a different block.  Somehow breaks OpenMP.  Don't
      know OpenMP, so cannot judge whether branching to a different block
      is allowed.
95543 Not in mega patch.  Fixes a PDT issue, but PDT are so horribly 
      broken the result produces wrong code.

I also have very old patches for pr30371 and pr69101, which
I have not tried to merge into my local git repository.

I guess I can start over with

% git clone git://gcc.gnu.org/git/gcc.git DIR1
% cp -R DIR1 DIR2
(merge changes into DIR1)
% diff -NR DIR2 DIR1

-- 
steve

      parent reply	other threads:[~2021-03-14 16:47 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
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 [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=20210314164656.GA5869@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=burnus@net-b.de \
    --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).