[PATCH] Fix fortran/81509

[Steve Kargl]

On Tue, Oct 03, 2017 at 09:38:51PM +0200, Janus Weil wrote:
> 2017-10-03 20:10 GMT+02:00 Steve Kargl <sgk@troutmask.apl.washington.edu>:
> >> > There is no mechanism available to warn the user of nonstandard code.
> >>
> >> Of course there is:
> >>
> >> $ gfortran -std=f2008 a.f90
> >> a.f90:4:17:
> >>
> >>     print *, iand(i,j)
> >>                  1
> >> Error: GNU Extension: Different type kinds at (1)
> >>
> >
> > Reread what I wrote.  There is NO MECHANISM TO WARN the user.
> > -std=f2008 does not produce a WARNING.  It produces an ERROR.
> 
> Sorry, I'm currently traveling and must have misread that.
> 
> Anyway, I don't have the feeling this discussion is going anywhere. I
> said my opinion, you heard it. You have two OKs, so just go ahead and
> commit the patch. I really don't care.
> 

That's two us.  I really don't care.  I don't use IAND, IOR, IEOR, AND, OR,
or XOR.  I simply supplied a patch that brings gfortran into conformance
with F2008.  It sparked controversy.  I withdrew the patch.  The changes
are no longer in my local tree, so I won't be committing anything.  I've
moved onto other things.

For record, my controversal patch fixed

% cat a.f90
program foo
  print '(2(I0,1X))', iand(42,z'dead'), kind(iand(42,z'dead'))
  print '(2(I0,1X))', iand(z'dead',42), kind(iand(z'dead',42))
end program foo
% gfortran6 -static -o z a.f90 && ./z
40 4
40 8

-- 
Steve
20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
20161221 https://www.youtube.com/watch?v=IbCHE-hONow