I am sorry, but the initial mail as well as Dominique answer puzzles me:
David: I do expect to
write (*,*) any
not being compilable at all, because "any" is an intrinsic function and I
suppose that gfortran is not able to print it. At best it gives an address. So
am I right to assume that it should have been:
write (*,*) x
Which is a bit strange. Furthermore is it difficult for me to debug, because I
do not have access to an AIX machine. What address size does the machine have
32/48/64-bit? Is there a chance you send me the file that is generated
additionally by gfortran when called with -fdump-tree-original ? The file is
named alloc_comp_class_5.f03.003t.original usually.
Dominique: How did you get that? Do you have access to an AIX machine? What
kind of instrumentation was active in the compiler you mentioned?
On Wed, 30 Nov 2016 21:51:30 +0100
Dominique d'Humières <domi...@lps.ens.fr> wrote:
> If I compile the test with an instrumented gfortran , I get
> ../../work/gcc/fortran/interface.c:2948:33: runtime error: load of value
> 1818451807, which is not a valid value for type ‘expr_t'
> > Le 30 nov. 2016 à 21:06, David Edelsohn <dje....@gmail.com> a écrit :
> > Hi, Andre
> > I have noticed that the alloc_comp_class_5.f03 testcase fails on AIX.
> > Annotating the testcase a little, shows that the failure is at
> > if (any(x /= ["foo", "bar", "baz"])) call abort()
> > write (*,*) any
> > at the point of failure produces
> > "foobarba"
> > - David
Andre Vehreschild * Email: vehre ad gmx dot de