public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49324] iso_varying_string and reshape fail
Date: Wed, 08 Jun 2011 16:23:00 -0000	[thread overview]
Message-ID: <bug-49324-4-y3aXMFWIzY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49324-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49324

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-06-08 16:22:37 UTC ---
Not an analysis, just some observations ...

I get different results with different compilers:
gfortran 4.7:
 array2d second            2           3 '' '@' '`' '`A�▒' '@' 'A�'
ifort 11.1:
  array2d second            2           3 '/' '/' '/' '/' '/' '/'
NAG 5.1 and pgf90 10.1-0:
  array2d second  2 3 '' '' '' 'four' '' ''
pathf95 and g95:
 array2d second  2 3 '1' '2' '3' 'four' '5' 'six'

[Neither NAG with -C=all -C=undefined, nor ifort -check all, nor gfortran
-fcheck=all show an error.]


I tried also the other ISO Varying String implementations at
ftp://ftp.nag.co.uk/sc22wg5/ISO_VARYING_STRING/Sample_Module/ , but I fail to
get a consistent result with those.

ifort with either iso_vst.f90 or iso_vsta.f90:
 array2d second            2           3 '1' '1' '1' '1' '1' '1'
gfortran, g95, NAG, pgf90 and pathf95 with iso_vst.f90
and with g95, pgf90 and pathf95 for iso_vsta.f90:
 array2d second            2           3 '1' '2' '3' 'four' '5' 'six'
gfortran with iso_vsta.f90:
 array2d second            2           3 '' '�' '�' '�jb' '�' 'b'
NAG with iso_vsta.f90:
  ALLOCATABLE array allocatable array component is not currently allocated
  Program terminated by fatal error
  In S_ASS_S, line 342 of iso_vsta.f90
  Called by TEST_IVS, line 13 of hj4f.f90


  reply	other threads:[~2011-06-08 16:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 15:07 [Bug fortran/49324] New: " jjcogliati-r1 at yahoo dot com
2011-06-08 16:23 ` burnus at gcc dot gnu.org [this message]
2011-06-08 16:30 ` [Bug fortran/49324] " jjcogliati-r1 at yahoo dot com
2011-06-08 22:13 ` burnus at gcc dot gnu.org
2011-06-09  7:27 ` [Bug fortran/49324] Deep copy missing for array constructors of DT w/ allocatable components burnus at gcc dot gnu.org
2011-06-09 22:23 ` burnus at gcc dot gnu.org
2011-06-10  8:35 ` burnus at gcc dot gnu.org
2011-06-10 12:45 ` burnus at gcc dot gnu.org
2011-06-11 22:09 ` burnus at gcc dot gnu.org
2011-06-14 13:08 ` burnus at gcc dot gnu.org
2011-06-17  6:12 ` burnus at gcc dot gnu.org
2011-07-11 16:38 ` jjcogliati-r1 at yahoo dot com
2011-07-11 16:53 ` burnus at gcc dot gnu.org
2023-06-21  9:27 ` damian at archaeologic dot codes

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=bug-49324-4-y3aXMFWIzY@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).