From: Andre Vehreschild <vehre@gmx.de>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: [Fortran, Patch, PR{43366, 57117, 61337, 61376}, v1] Assign to polymorphic objects.
Date: Thu, 01 Dec 2016 18:32:00 -0000 [thread overview]
Message-ID: <20161201193158.1877e21f@vepi2> (raw)
In-Reply-To: <8FE89D89-40DB-4967-A154-A1EB3F5566D0@lps.ens.fr>
Hi all,
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?
- Andre
On Wed, 30 Nov 2016 21:51:30 +0100
Dominique d'Humières <dominiq@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'
>
> Dominique
>
> > Le 30 nov. 2016 à 21:06, David Edelsohn <dje.gcc@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
next prev parent reply other threads:[~2016-12-01 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 20:06 David Edelsohn
2016-11-30 20:51 ` Dominique d'Humières
2016-12-01 18:32 ` Andre Vehreschild [this message]
2016-12-01 18:56 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2016-10-22 12:22 Paul Richard Thomas
2016-10-22 13:44 ` Andre Vehreschild
2016-10-13 15:16 Andre Vehreschild
2016-10-19 18:02 ` Andre Vehreschild
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=20161201193158.1877e21f@vepi2 \
--to=vehre@gmx.de \
--cc=dje.gcc@gmail.com \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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).