public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36528] Cray pointer to function mishandled
Date: Wed, 11 Feb 2009 15:09:00 -0000 [thread overview]
Message-ID: <20090211150851.3206.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36528-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pault at gcc dot gnu dot org 2009-02-11 15:08 -------
This fixes the bug. I need to look at the passing of Cray pointers in general
because it looks a bit shakey to me.
trans-expr.c:
2626c2626,2637
< if (fsym && fsym->attr.value)
---
> if (fsym && fsym->attr.flavor == FL_PROCEDURE
> && e->expr_type == EXPR_VARIABLE
> && e->symtree->n.sym->attr.cray_pointee)
> {
> /* The Cray pointer needs to be converted to a pointer type
> pointee. The symbol gives the pointee address. */
> gfc_conv_expr (&parmse, e);
> type = build_pointer_type (TREE_TYPE (parmse.expr));
> tmp = gfc_get_symbol_decl (e->symtree->n.sym->cp_pointer);
> parmse.expr = convert (type, tmp);
> }
> else if (fsym && fsym->attr.value)
Cheers
Paul
--
pault at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |pault at gcc dot gnu dot org
|dot org |
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-02-11 15:08:51
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36528
next prev parent reply other threads:[~2009-02-11 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 14:30 [Bug fortran/36528] New: " burnus at gcc dot gnu dot org
2008-06-13 16:55 ` [Bug fortran/36528] " burnus at gcc dot gnu dot org
2009-02-11 15:09 ` pault at gcc dot gnu dot org [this message]
2009-02-13 21:13 ` pault at gcc dot gnu dot org
2009-03-28 17:09 ` pault at gcc dot gnu dot org
2009-03-28 17:39 ` pault at gcc dot gnu dot org
2009-04-06 11:07 ` pault at gcc dot gnu dot 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=20090211150851.3206.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).