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/48011] internal compiler error:tree check: expected function_type or method_type, have pointer_type in gimplify_call_expr at gimplify.c:2355
Date: Mon, 07 Mar 2011 08:40:00 -0000	[thread overview]
Message-ID: <bug-48011-4-ljV0goY2M1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48011-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #3 from janus at gcc dot gnu.org 2011-03-07 08:39:23 UTC ---
(In reply to comment #1)
> This looks like a duplicate of pr46262 (cc Janus).

Yes, it is in fact a duplicate of this PR. It is even derived from the same
code. The problem is this line:

model = model + d_dt(model)*dt   ! Explicit Euler formula

"+" and "*" here are user-defined polymorphic operators, and "d_dt" has a
polymorphic result. For properly generating the type-bound calls to the two
operators, we need to insert temporaries for the passed objects. This does not
work currently.

*** This bug has been marked as a duplicate of bug 46262 ***


      parent reply	other threads:[~2011-03-07  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06 21:25 [Bug fortran/48011] New: " dominique.pelletier at polymtl dot ca
2011-03-06 22:20 ` [Bug fortran/48011] " dominiq at lps dot ens.fr
2011-03-07  3:22 ` jvdelisle at gcc dot gnu.org
2011-03-07  8:40 ` janus at gcc dot gnu.org [this message]

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-48011-4-ljV0goY2M1@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).