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/31200] wrong code: procedure call with pointer-returning-function as argument
Date: Fri, 16 Mar 2007 17:10:00 -0000 [thread overview]
Message-ID: <20070316171034.28970.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31200-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pault at gcc dot gnu dot org 2007-03-16 17:10 -------
(In reply to comment #1)
> real4 D.1254;
> D.1254 = *f (&x);
> s3 (&D.1254);
> }
> instead of
> D.1254 = f(&x)
Funnily enough, I have been hit by the same problem in implementing procedure
pointers. I will attempt to come to grips with it.
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|NEW |ASSIGNED
Last reconfirmed|2007-03-16 14:07:34 |2007-03-16 17:10:34
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31200
next prev parent reply other threads:[~2007-03-16 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 11:27 [Bug fortran/31200] New: wrong code generated with gfortran jv244 at cam dot ac dot uk
2007-03-16 14:07 ` [Bug fortran/31200] wrong code: procedure call with pointer-returning-function as argument burnus at gcc dot gnu dot org
2007-03-16 17:10 ` pault at gcc dot gnu dot org [this message]
2007-03-17 15:53 ` pault at gcc dot gnu dot org
2007-03-21 17:13 ` burnus at gcc dot gnu dot org
2007-03-24 8:10 ` patchapp at dberlin dot org
2007-03-24 12:31 ` pault at gcc dot gnu dot org
2007-03-24 13:58 ` pault at gcc dot gnu dot org
2007-03-24 14:18 ` 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=20070316171034.28970.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).