public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29962] Initialization expressions
Date: Tue, 24 Jul 2007 18:41:00 -0000 [thread overview]
Message-ID: <20070724184136.2107.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29962-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from dfranke at gcc dot gnu dot org 2007-07-24 18:41 -------
Changed the title as init expressions are not restricted to the previously
named function.
The following is a list of items I am aware of that need to be done before init
expressions are complete:
TODO for F95, 7.1.6.1:
* nothing?!
TODO for F2003, 7.1.6, Specification Inquiry:
* "(7)a type parameter inquiry (6.1.3)"
TODO for F2003, 7.1.7:
* simplifiers for transformational intrinsics other than those listed by F95
* anything related to IEEE (see also PR29383)
* "(9) A kind type parameter of the derived type being defined"
Please add to this list whatever I may have missed :)
--
dfranke at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Initialization expressions |Initialization expressions
|checking in |
|gfc_intrinsic_func_interface|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29962
next prev parent reply other threads:[~2007-07-24 18:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 20:35 [Bug fortran/29962] New: Initialization expressions checking in gfc_intrinsic_func_interface burnus at gcc dot gnu dot org
2006-11-23 21:10 ` [Bug fortran/29962] " burnus at gcc dot gnu dot org
2006-11-23 21:59 ` burnus at gcc dot gnu dot org
2006-11-23 23:52 ` burnus at gcc dot gnu dot org
2006-11-24 7:20 ` burnus at gcc dot gnu dot org
2006-11-27 10:15 ` patchapp at dberlin dot org
2006-12-04 20:03 ` burnus at gcc dot gnu dot org
2007-03-06 7:57 ` fxcoudert at gcc dot gnu dot org
2007-06-23 16:13 ` burnus at gcc dot gnu dot org
2007-07-22 16:32 ` dfranke at gcc dot gnu dot org
2007-07-24 13:32 ` burnus at gcc dot gnu dot org
2007-07-24 18:41 ` dfranke at gcc dot gnu dot org [this message]
2007-10-05 19:52 ` [Bug fortran/29962] Initialization expressions tobi at gcc dot gnu dot org
2009-03-23 19:57 ` dfranke at gcc dot gnu dot org
2009-03-23 20:04 ` dfranke at gcc dot gnu dot org
2009-03-31 20:02 ` dfranke at gcc dot gnu dot org
2009-04-05 20:40 ` dfranke at gcc dot gnu dot org
2009-04-10 14:04 ` dfranke at gcc dot gnu dot org
2009-06-07 11:53 ` burnus at gcc dot gnu dot org
2009-06-07 16:35 ` burnus at gcc dot gnu dot org
2009-06-07 17:34 ` burnus at gcc dot gnu dot org
2009-12-04 22:07 ` dfranke at gcc dot gnu dot org
[not found] <bug-29962-4@http.gcc.gnu.org/bugzilla/>
2013-06-25 17:17 ` 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=20070724184136.2107.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).