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/54618] [OOP] wrong-code with CLASS(...), INTENT(OUT) -- and OPTIONAL or ALLOCATABLE
Date: Wed, 03 Oct 2012 14:20:00 -0000 [thread overview]
Message-ID: <bug-54618-4-3U1sZgPIsF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54618-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54618
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #28304|0 |1
is obsolete| |
--- Comment #14 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-10-03 14:20:22 UTC ---
Created attachment 28341
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28341
Updated OPTIONAL patch
Current version of my OPTIONAL patch. Changes:
- polymorphic scalar coarray to polymorphic noncoarrays work now
- Much extended test case (and plenty of new FIXMEs)
TODO: Fix those FIXMEs.
Other TODO items:
- Support packing of assumed-rank arrays
(see just attached test case; but otherwise an unrelated issue)
- Fix INTENT(OUT) handling for allocatable polymorphic arrays (cf. comment 0)
- Analyse the old issue related to class_array_7.f03 (comment 11, comment 12)
next prev parent reply other threads:[~2012-10-03 14:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 15:24 [Bug fortran/54618] New: " burnus at gcc dot gnu.org
2012-09-19 8:18 ` [Bug fortran/54618] " burnus at gcc dot gnu.org
2012-09-19 13:31 ` burnus at gcc dot gnu.org
2012-09-19 17:31 ` burnus at gcc dot gnu.org
2012-09-19 20:18 ` mikael at gcc dot gnu.org
2012-09-22 17:07 ` burnus at gcc dot gnu.org
2012-09-23 6:49 ` burnus at gcc dot gnu.org
2012-09-24 19:05 ` burnus at gcc dot gnu.org
2012-09-25 14:20 ` burnus at gcc dot gnu.org
2012-09-25 18:37 ` burnus at gcc dot gnu.org
2012-09-26 5:51 ` burnus at gcc dot gnu.org
2012-09-30 12:51 ` dominiq at lps dot ens.fr
2012-09-30 17:01 ` burnus at gcc dot gnu.org
2012-09-30 18:02 ` burnus at gcc dot gnu.org
2012-10-03 14:20 ` burnus at gcc dot gnu.org [this message]
2012-10-03 17:32 ` burnus at gcc dot gnu.org
2012-10-16 13:02 ` burnus at gcc dot gnu.org
2012-10-16 13:13 ` burnus at gcc dot gnu.org
2013-04-05 9:32 ` sfilippone at uniroma2 dot it
2013-04-05 9:33 ` sfilippone at uniroma2 dot it
2013-04-05 11:35 ` burnus at gcc dot gnu.org
2013-04-05 12:29 ` sfilippone at uniroma2 dot it
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-54618-4-3U1sZgPIsF@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).