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/46641] Specification-expr checks and results with C_SIZEOF and SIZEOF
Date: Wed, 24 Nov 2010 15:13:00 -0000 [thread overview]
Message-ID: <bug-46641-4-v7IDyhcie5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46641-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46641
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |36437, 45824
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-11-24 14:53:27 UTC ---
(In reply to comment #0)
> In terms of validity, the question is whether
> C_SIZEOF (structure-constructor ())
> is a valid initialization expression -- gfortran accepts it.
I marked the PR now as regression as gfortran 4.5 accepts it - but does not
have the segfault issue at run time.
That issue seems to be related to the compile-time simplification - or rather
the lack of. Both 4.5 and 4.6 produce the dump:
character(kind=1) str[1:.str];
TODO:
a) Fix the issue above, cf. PR 36437
b) decide which of the various c_sizeof/sizeof is valid and thus should be
accepted or rejected; look also at the the thread (cf. comment 0) and in
particular at
http://groups.google.com/group/comp.lang.fortran/msg/8b36b578793b7037 , cf.
also PR 45824
next prev parent reply other threads:[~2010-11-24 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 14:45 [Bug fortran/46641] New: " burnus at gcc dot gnu.org
2010-11-24 15:13 ` burnus at gcc dot gnu.org [this message]
2010-11-24 18:23 ` [Bug fortran/46641] " kargl at gcc dot gnu.org
2010-11-27 22:20 ` burnus at gcc dot gnu.org
2013-06-20 22:04 ` dominiq at lps dot ens.fr
2013-06-20 22:07 ` dominiq at lps dot ens.fr
2013-12-14 20:13 ` dominiq at lps dot ens.fr
2013-12-14 20:25 ` 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-46641-4-v7IDyhcie5@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).