public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/27997] Fortran 2003: Support type-spec for array constructor
Date: Tue, 01 Apr 2008 10:18:00 -0000 [thread overview]
Message-ID: <20080401101728.28831.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27997-1719@http.gcc.gnu.org/bugzilla/>
------- Comment #16 from burnus at gcc dot gnu dot org 2008-04-01 10:17 -------
(In reply to comment #15)
> However, the following program without typespec in the array constructor also
> fails (according to my judging what it should do)
Different compilers give different output for this one, but this is no problem
as the program is invalid. "gfortran -fbounds-check" shows the problem:
Fortran runtime error: Different CHARACTER lengths (4/5) in array constructor
That is the reason why (/ typespec :: element-list /) is needed. How long
should be each element for (/ "a", "bb", "ccc" /) ? One, two, three or ...
characters? One could argue that is should match the longest, but this is an
arbitrary choice and makes the run-time array construction slower. Actually,
with the Intel compiler, 's, "test"' and '"test", s' produce different results
;-)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27997
next prev parent reply other threads:[~2008-04-01 10:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 13:03 [Bug fortran/27997] New: Fortran 2003: Support type-spec for array constructor, i.e. (/ real :: 1., 2., 3. /) tobias dot burnus at physik dot fu-berlin dot de
2006-09-28 8:02 ` [Bug fortran/27997] Fortran 2003: Support type-spec for array constructor fxcoudert at gcc dot gnu dot org
2007-11-08 18:59 ` fxcoudert at gcc dot gnu dot org
2007-12-14 16:24 ` burnus at gcc dot gnu dot org
2007-12-14 17:20 ` burnus at gcc dot gnu dot org
2008-03-24 20:02 ` d at domob dot eu
2008-03-25 12:44 ` d at domob dot eu
2008-03-25 12:51 ` fxcoudert at gcc dot gnu dot org
2008-03-25 12:59 ` fxcoudert at gcc dot gnu dot org
2008-03-25 16:05 ` burnus at gcc dot gnu dot org
2008-03-25 16:41 ` d at domob dot eu
2008-03-25 16:55 ` fxcoudert at gcc dot gnu dot org
2008-03-25 17:11 ` d at domob dot eu
2008-03-25 19:54 ` d at domob dot eu
2008-03-28 10:32 ` burnus at gcc dot gnu dot org
2008-04-01 8:13 ` d at domob dot eu
2008-04-01 10:18 ` burnus at gcc dot gnu dot org [this message]
2008-04-01 12:54 ` d at domob dot eu
2008-04-01 14:18 ` burnus at gcc dot gnu dot org
2008-04-04 20:27 ` d at domob dot eu
2008-04-04 22:44 ` burnus at gcc dot gnu dot org
2008-04-06 15:29 ` d at domob dot eu
2008-04-06 16:23 ` burnus at gcc dot gnu dot org
2008-04-08 13:12 ` d at domob dot eu
2008-04-11 20:27 ` d at domob dot eu
2008-05-16 19:51 ` burnus at gcc dot gnu dot org
2008-05-16 19:55 ` burnus at gcc dot gnu dot org
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=20080401101728.28831.qmail@sourceware.org \
--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).