public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janus Weil <janus@gcc.gnu.org>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
	gfortran <fortran@gcc.gnu.org>,
		gcc-patches <gcc-patches@gcc.gnu.org>,
	neil.n.carlson@gmail.com
Subject: Re: [Patch, Fortran] PR 84273: Reject allocatable passed-object dummy argument (proc_ptr_47.f90)
Date: Sun, 11 Feb 2018 13:42:00 -0000	[thread overview]
Message-ID: <CAKwh3qhgs0vWo9dZyML0YyzSo4TLfZ31OmLBpj=XDeUfG-8ahQ@mail.gmail.com> (raw)
In-Reply-To: <CAGkQGiJQ-xjLKHmnEtY1xALzh5ORyBg_EXcFW9aLfyzKpvRSpA@mail.gmail.com>

Hi guys,

2018-02-10 12:46 GMT+01:00 Paul Richard Thomas <paul.richard.thomas@gmail.com>:
> As Steve said, welcome back!

thanks for the warm welcome :)


> I hope that you will post the news of this fix and the correction of
> the testcases on clf. Talking of which, have you posted the problems
> that others have found as PRs?

Well, I have opened PR 84094 as a collector for such things (and a few
dependencies). Neil Carson has put a great amount of work into
analyzing some of the issues that came up and compiled a very helpful
list at:

https://github.com/nncarlson/gfortran.dg/issues

I have not sifted through the extensive c.l.f. thread (which may
contain further possible issues posted by people who lack the skills
to use any kind of bug tracker), any I don't have the intention
(read:time) to do that.


> It was one of my long deferred tasks to make a start on validating the
> testsuite and to remove non-standard features.

The biggest issue in this respect is probably the frequent use of the
non-std "call abort". All of those could simply be replaced by "stop
1" AFAICS, and if there is consensus that this is a useful thing to
do, I'd be willing to take care of it. (Feedback welcome here).

Cheers,
Janus

  reply	other threads:[~2018-02-11 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 17:13 Janus Weil
2018-02-09 23:21 ` Steve Kargl
2018-02-10 11:46   ` Paul Richard Thomas
2018-02-11 13:42     ` Janus Weil [this message]
2018-02-11 21:44   ` Janus Weil
2018-02-12  7:22     ` Richard Biener
2018-02-12 17:14       ` Janus Weil

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='CAKwh3qhgs0vWo9dZyML0YyzSo4TLfZ31OmLBpj=XDeUfG-8ahQ@mail.gmail.com' \
    --to=janus@gcc.gnu.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=neil.n.carlson@gmail.com \
    --cc=paul.richard.thomas@gmail.com \
    --cc=sgk@troutmask.apl.washington.edu \
    /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).