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/49278] internal compiler error: Segmentation fault
Date: Mon, 06 Jun 2011 08:23:00 -0000 [thread overview]
Message-ID: <bug-49278-4-QZpZVX814f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49278-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49278
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-06-06 08:22:53 UTC ---
(In reply to comment #2)
> The following aborts. Note sure if it is conforming.
* ifort (also w/ "-stand f03 -warn all") and PGI accept it - and have the
expected value
* NAG 5.1 and g95 have %d == 0, i.e. the explicit DATA initialization prevents
the default initialization of trlkold.
* pathf95/openf95/crayftn/sunf95 reject the DATA because there is a default
initialization
It's actually a difficult to see whether it is invalid or not. However, I think
the code is valid (taking the side of NAG and g95): One does not do any double
initialization. From the F2008 standard:
"If a nonpointer object has default initialization, it shall not appear in a
data-stmt-object-list." (5.4.7 DATA statement) -- Does not seem to apply as
"trlkold%v" is not default initialized.
"5.2.3 Initialization":
"Explicit initialization alternatively may be specified in a DATA statement
unless the variable is of a derived type for which default initialization is
specified." -- Ditto.
"A variable, or part of a variable, shall not be explicitly initialized more
than once in a program." -- Also this is not violated.
Hence, it seems to be valid, but I wouldn't mind if someone could cross check,
given that most compilers don't generate the expected result - and given that
reading the standard can be difficult. [Even J3/WG5 members might read it
differently.]
next prev parent reply other threads:[~2011-06-06 8:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 15:19 [Bug fortran/49278] New: " petrielmjr at ornl dot gov
2011-06-03 16:08 ` [Bug fortran/49278] " kargl at gcc dot gnu.org
2011-06-03 18:11 ` sgk at troutmask dot apl.washington.edu
2011-06-06 8:23 ` burnus at gcc dot gnu.org [this message]
2011-06-07 9:17 ` [Bug fortran/49278] ICE (segfault) when combining DATA with default initialization burnus at gcc dot gnu.org
2011-06-08 5:55 ` burnus at gcc dot gnu.org
2011-06-14 12:32 ` burnus at gcc dot gnu.org
2011-06-30 12:26 ` thenlich at users dot sourceforge.net
2011-06-30 12:34 ` burnus at gcc dot gnu.org
2020-12-22 20:36 ` anlauf at gcc dot gnu.org
2020-12-22 20:43 ` anlauf at gcc dot gnu.org
2020-12-22 21:24 ` kargl at gcc dot gnu.org
2020-12-22 21:31 ` kargl at gcc dot gnu.org
2020-12-22 21:34 ` anlauf at gcc dot gnu.org
2020-12-22 21:36 ` anlauf at gcc dot gnu.org
2020-12-22 21:49 ` kargl at gcc dot gnu.org
2021-03-01 22:17 ` anlauf at gcc dot gnu.org
2021-03-08 21:00 ` cvs-commit at gcc dot gnu.org
2021-03-09 8:34 ` zeccav at gmail dot com
2024-04-04 19:54 ` anlauf at gcc dot gnu.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=bug-49278-4-QZpZVX814f@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).