This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH(es)] PR fortran/77391 -- RFC vote on which you prefer
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Mikael Morin <morin-mikael at orange dot fr>
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Fri, 26 Aug 2016 13:38:12 -0700
- Subject: Re: [PATCH(es)] PR fortran/77391 -- RFC vote on which you prefer
- Authentication-results: sourceware.org; auth=none
- References: <20160826182755.GA63696@troutmask.apl.washington.edu> <c402a0eb-9c23-9d87-5cfd-1b8c01a79fd7@orange.fr>
- Reply-to: kargl at uw dot edu
On Fri, Aug 26, 2016 at 10:28:25PM +0200, Mikael Morin wrote:
> Hello,
>
> Le 26/08/2016 à 20:27, Steve Kargl a écrit :
> > Here are two possible patches for PR fortran/77391. The first
> > patch treats the invalid code as a GNU Fortran extension as
> > gfortran current accepts the invalid code. The second patch
> > enforces the standard. As I think gfortran should encourage
> > standard conformance, I am inclined to commit the second patch.
> > I will however commit the most popular of the two patches tomorrow.
> > Voting starts now and will remain open for 24 hours (give or take
> > a few hours depend on when I awaken).
> >
>
> I don't think it's sufficient to check current_attr because of this case:
>
> character(:) :: a
> pointer :: a
> end
>
> The statement should be accepted, and the check be postponed at a time
> after the symbol has been initialised, at resolution time for example.
Hmmm, yes indeed. I guess I'll need to wade through resolve.c.
--
Steve