[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-fortran
Subject:    Re: [Patch, fortran] PRs 89843 and 90022 - C Fortran Interop fixes.
From:       Paul Richard Thomas <paul.richard.thomas () gmail ! com>
Date:       2019-04-26 17:41:31
Message-ID: CAGkQGiKP=f8kKViUbYL=qhky+XikM3CAcYYXwkbQtWOMpu6H+g () mail ! gmail ! com
[Download RAW message or body]

Hi Manfred,

I took a look at it and couldn't see what the problem is. I'll have
another stab at it tomorrow morning.

Cheers

Paul

On Fri, 26 Apr 2019 at 16:39, Manfred Schwarb <manfred99@gmx.ch> wrote:
>
> Hi,
>
> I still see this issue on 32bit, is the plan to let
> the test ISO_Fortran_binding_4.f90 be broken for the 9.0 release?
>
> Cheers,
> Manfred
>
>
> Am 15.04.19 um 10:30 schrieb Dominique d'Humières:
> > Hi Paul,
> >
> > I have found another glitch with -m32 and -O1 or -Os, but not with other values:
> >
> > % gfc /opt/gcc/_clean/gcc/testsuite/gfortran.dg/ISO_Fortran_binding_4.f90 -m32 -O
> > % ./a.out
> >  FAIL
> > Note: The following floating-point exceptions are signalling: IEEE_DENORMAL
> > STOP 1
> >
> > This looks tricky: if I add a line
> >
> >   print *, x
> >
> > before
> >
> >   if (any (abs (x - [1.,20.,3.,40.,5.,60.]) > 1.e-6)) stop 2
> >
> > the test succeeds!-(
> >
> > Also you don't want pr89844 to be solved, don't you?
> >
> > TIA
> >
> > Dominique
> >
> >
> >> Le 11 avr. 2019 à 16:44, Paul Richard Thomas <paul.richard.thomas@gmail.com> a écrit :
> >>
> >> Hi Dominique,
> >>
> >> Yes indeed - I used int(kind(loc(res))) to achieve the same effect.
> >>
> >> I am looking for but failing to find a similar problem for PR89846.
> >> Tomorrow I turn my attention to an incorrect cast in the compiler.
> >>
> >> Regards
> >>
> >> Paul
> >
> >
>


-- 
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein
[prev in list] [next in list] [prev in thread] [next in thread]