public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: Fortran List <fortran@gcc.gnu.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR fortran/91943 -- More BOZ fallout
Date: Fri, 11 Oct 2019 14:56:00 -0000	[thread overview]
Message-ID: <CAO9iq9HA8DmueUa+tiC2B4QpZE0qfs78hrRwZLCsridhAwRdZg@mail.gmail.com> (raw)
In-Reply-To: <20190930222308.GA2502@troutmask.apl.washington.edu>

On Tue, Oct 1, 2019 at 1:23 AM Steve Kargl
<sgk@troutmask.apl.washington.edu> wrote:
>
> A BOZ cannot be an actual argument in a subroutine or function
> reference except those intrinsic function listed in the Fortran
> standard.  The attach patch checks for invalid BOZ.  Built and
> tested on x86_64-*-freebsd.  OK to commit?
>
> 2019-09-30  Steven G. Kargl  <kargl@gcc.gnu.org>
>
>         PR fortran/91943
>         * match.c (gfc_match_call): BOZ cannot be an actual argument in
>         a subroutine reference.
>         * resolve.c (resolve_function): BOZ cannot be an actual argument in
>         a function reference.
>
> 2019-09-30  Steven G. Kargl  <kargl@gcc.gnu.org>
>
>         PR fortran/91943
>         gfortran.dg/pr91943.f90
>
> --
> Steve

Ok, though I believe your other BOZ patch that I just reviewed applies
on top of this one?

-- 
Janne Blomqvist

  reply	other threads:[~2019-10-11 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30 22:23 Steve Kargl
2019-10-11 14:56 ` Janne Blomqvist [this message]
2019-10-11 15:34   ` 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=CAO9iq9HA8DmueUa+tiC2B4QpZE0qfs78hrRwZLCsridhAwRdZg@mail.gmail.com \
    --to=blomqvist.janne@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --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).