public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52994] [OOP] [F08] internal compiler error: in gfc_trans_assignment_1, at fortran/trans-expr.c:6881
Date: Sun, 15 Apr 2012 18:46:00 -0000	[thread overview]
Message-ID: <bug-52994-4-tn2TXJyArA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52994-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-04-15
                 CC|                            |janus at gcc dot gnu.org
         Depends on|                            |40054
            Summary|internal compiler error: in |[OOP] [F08] internal
                   |gfc_trans_assignment_1, at  |compiler error: in
                   |fortran/trans-expr.c:6881   |gfc_trans_assignment_1, at
                   |                            |fortran/trans-expr.c:6881
     Ever Confirmed|0                           |1

--- Comment #2 from janus at gcc dot gnu.org 2012-04-15 18:46:39 UTC ---
ICE Confirmed with 4.6, 4.7 and trunk.

I think the test case is invalid in F03, but should be valid in F08: It makes
use of pointer functions as lvalue, which is PR40054.

However, it does not just use a 'plain' pointer function, but even a
pointer-valued (and dimensionful) type-bound procedure. Phew. Thanks for the
nice test case :)


  parent reply	other threads:[~2012-04-15 18:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 11:40 [Bug fortran/52994] New: " slayoo at staszic dot waw.pl
2012-04-15 11:41 ` [Bug fortran/52994] " slayoo at staszic dot waw.pl
2012-04-15 18:46 ` janus at gcc dot gnu.org [this message]
2012-04-15 19:28 ` [Bug fortran/52994] [OOP] [F08] " slayoo at staszic dot waw.pl
2012-04-15 19:32 ` janus at gcc dot gnu.org
2012-04-15 19:37 ` janus at gcc dot gnu.org
2012-04-15 19:41 ` janus at gcc dot gnu.org
2012-04-15 19:43 ` janus at gcc dot gnu.org
2012-04-15 20:24 ` slayoo at staszic dot waw.pl
2012-04-15 20:41 ` janus at gcc dot gnu.org
2012-04-16  9:05 ` janus at gcc dot gnu.org
2012-04-16  9:11 ` janus at gcc dot gnu.org
2015-09-28 21:27 ` pault at gcc dot gnu.org
2023-10-12 14:31 ` pault 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-52994-4-tn2TXJyArA@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).