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/51605] internal compiler error gfc_trans_block_construct, at fortran/trans-stmt.c:984
Date: Sun, 18 Dec 2011 14:15:00 -0000	[thread overview]
Message-ID: <bug-51605-4-gOtyoDQJeb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51605-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51605

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |rejects-valid

--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-12-18 14:11:00 UTC ---
(In reply to comment #5)
> Therefore I believe it's conforming to point to the associating entity with a
> typed pointer.
> (integer_ptr => symbol_ptr)

I should have read the test case more carefully. The associate name is on the
right and not on the left hand side. I concur that in this case the associate
name should get the target attribute. Thanks for pointing that out!


> I'm using the gfortran I'm using because it had a Mac installer.  I thought
> 4.6.2 was fairly recent.

Yes, 4.6.2 is the latest release; however, the 4.6 branch is now 9 months old
and thus misses all the changes for 4.7, which will be released in March. [The
trunk (= main development line) is currently in the stabilization and bug
fixing Stage 3.]

As Fortran's polymorphism support is quite complicated, implementing it takes a
while and the current implementations are still incomplete and buggy. (That's
the case for all compilers, though the stability and completeness varies.)

In case of GCC/gfortran, 4.7 now supports constructors (DT name = generic
function name) and - since 2011-12-11 -polymorphic arrays. Additionally,
several other bugs were fixed. See http://gcc.gnu.org/wiki/OOP for an overview.

There is a fairly new 4.7 binary available for Darwin (cf.
http://gcc.gnu.org/wiki/GFortranBinaries#MacOS ) but the build is almost 4
weeks old and thus does not yet support polymorphic arrays. My idea was that I
will asked for a new build soon, but only after a few additional OOP bugs have
been fixed.


  parent reply	other threads:[~2011-12-18 14:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 22:46 [Bug fortran/51605] New: " danlnagle at me dot com
2011-12-17 23:26 ` [Bug fortran/51605] " danlnagle at me dot com
2011-12-17 23:48 ` dominiq at lps dot ens.fr
2011-12-18  9:24 ` kargl at gcc dot gnu.org
2011-12-18 10:08 ` burnus at gcc dot gnu.org
2011-12-18 13:55 ` danlnagle at me dot com
2011-12-18 14:15 ` burnus at gcc dot gnu.org [this message]
2011-12-18 16:57 ` sgk at troutmask dot apl.washington.edu
2011-12-19 11:52 ` burnus at gcc dot gnu.org
2011-12-19 13:19 ` burnus at gcc dot gnu.org
2011-12-19 15:32 ` burnus at gcc dot gnu.org
2011-12-19 15:54 ` danlnagle at me dot com
2011-12-19 18:56 ` burnus at gcc dot gnu.org
2011-12-19 20:26 ` burnus at gcc dot gnu.org
2011-12-19 20:30 ` burnus at gcc dot gnu.org
2013-12-14 20:15 ` dominiq at lps dot ens.fr
2013-12-14 22:25 ` janus at gcc dot gnu.org
2023-03-06 17:18 ` 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-51605-4-gOtyoDQJeb@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).