public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "w6ws at earthlink dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51976] [F2003] Support deferred-length character components of derived types (allocatable string length)
Date: Wed, 28 Aug 2013 22:33:00 -0000 [thread overview]
Message-ID: <bug-51976-4-aEjbQENhWF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51976-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51976
Walter Spector <w6ws at earthlink dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |w6ws at earthlink dot net
--- Comment #12 from Walter Spector <w6ws at earthlink dot net> ---
Adding myself (Walter Spector) to the cc list. My contribution is a simple
little test case that works with current versions of Intel (with -assume
realloc_lhs option) and NAG. As of todays gfortran snapshot (20130828), I get
a lot of 'Deferred-length character component 'city' at (1) is not yet
supported' errors.
program city_names
implicit none
type city_entry_t
character(:), allocatable :: city
character(:), allocatable :: state
end type
type(city_entry_t), allocatable :: cities(:)
integer :: i
cities = (/ &
city_entry_t ("San Francisco", "California"), &
city_entry_t ("Portland", "Oregon"), &
city_entry_t ("Seattle", "Washington"), &
city_entry_t ("Salt Lake City", "Utah"), &
city_entry_t ("Reno", "Nevada"), &
city_entry_t ("Tucson", "Arizona"), &
city_entry_t ("Denver", "Colorado"), &
city_entry_t ("Kansas City","Kansas"), &
city_entry_t ("Tulsa", "Oklahoma"), &
city_entry_t ("Houston", "Texas") &
/)
print '(5a)', (">",cities(i)%city, ", ", cities(i)%state,"<", i=1,size
(cities))
end program
next prev parent reply other threads:[~2013-08-28 22:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 8:05 [Bug fortran/51976] New: " burnus at gcc dot gnu.org
2012-01-24 8:08 ` [Bug fortran/51976] " burnus at gcc dot gnu.org
2012-01-24 8:14 ` burnus at gcc dot gnu.org
2012-01-24 8:35 ` burnus at gcc dot gnu.org
2012-01-24 8:37 ` burnus at gcc dot gnu.org
2012-05-14 16:45 ` burnus at gcc dot gnu.org
2012-11-08 15:00 ` burnus at gcc dot gnu.org
2013-01-30 6:16 ` pault at gcc dot gnu.org
2013-02-09 20:34 ` pault at gcc dot gnu.org
2013-02-10 19:59 ` dominiq at lps dot ens.fr
2013-02-25 8:49 ` burnus at gcc dot gnu.org
2013-05-20 9:23 ` burnus at gcc dot gnu.org
2013-06-05 9:20 ` burnus at gcc dot gnu.org
2013-08-28 22:33 ` w6ws at earthlink dot net [this message]
2014-02-19 15:54 ` janus at gcc dot gnu.org
2014-02-21 14:06 ` dominiq at lps dot ens.fr
2014-03-06 21:46 ` janus at gcc dot gnu.org
2014-06-03 19:54 ` jakub at gcc dot gnu.org
2014-11-16 15:35 ` dominiq at lps dot ens.fr
2015-04-23 12:58 ` vehre at gcc dot gnu.org
2015-09-03 21:18 ` dominiq at lps dot ens.fr
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-51976-4-aEjbQENhWF@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).