public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: "Dominique d'Humières" <dominiq@tournesol.lps.ens.fr>
Cc: "jvdelisle@charter.net" <jvdelisle@charter.net>,
	       gfortran <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH,fortran] Handle BOZ in accordance to Fortran 2018 standard (1st batch)
Date: Tue, 23 Jul 2019 21:57:00 -0000	[thread overview]
Message-ID: <20190723215035.GB19204@troutmask.apl.washington.edu> (raw)
In-Reply-To: <85000FF8-5C9B-4666-9047-F246412DC9F9@lps.ens.fr>

On Mon, Jul 22, 2019 at 02:33:08PM +0200, Dominique d'Humières wrote:
> (A) I see the following failures
> 
> FAIL: libgomp.fortran/reduction4.f90   -O0  (test for excess errors)
> …
> FAIL: libgomp.fortran/reduction5.f90   -Os  (test for excess errors)
> 

I added a fix for this to the megapatch.  It is rather slow
to test on i586-*-freebsd, so I tend to forget to test libgomp.

> (B) The points mentioned in
> https://gcc.gnu.org/ml/fortran/2017-10/msg00037.html have been fixed,
> except the points (3) and (6) which still give an ICE. I understand
> that the coddles are invalid,
>  but IMO they should give an error along the line
> 
> "BOZ literal at %L outside a DATA statement and outside INT/REAL/DBLE/CMPLX »
> 

I'll fix this shortly.  A BOZ is not allowed in transfer()
or storage_size().  I need to update check.c with a new
illegal_boz_arg() function and use it with the right checking
functions.

-- 
Steve

      reply	other threads:[~2019-07-23 21:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 13:27 Dominique d'Humières
2019-07-23 21:57 ` 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=20190723215035.GB19204@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=dominiq@tournesol.lps.ens.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).