public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32580] iso_c_binding c_f_procpointer / procedure pointers
Date: Mon, 02 Jun 2008 15:33:00 -0000 [thread overview]
Message-ID: <20080602153222.18803.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32580-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from burnus at gcc dot gnu dot org 2008-06-02 15:32 -------
Another link dump:
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/ff7ae6c7a7860bca/60213205751117d4
Some of the test cases should be checked when the proc pointer patch is ready
to ensure all are passed. (Forward carrying this link from PR 36322 which is
about to be fixed.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32580
next prev parent reply other threads:[~2008-06-02 15:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 7:20 [Bug fortran/32580] New: iso_c_binding c_f_procpointer jv244 at cam dot ac dot uk
2007-07-02 7:37 ` [Bug fortran/32580] " jv244 at cam dot ac dot uk
2007-07-02 14:57 ` kargl at gcc dot gnu dot org
2007-07-04 18:29 ` [Bug fortran/32580] iso_c_binding c_f_procpointer / procedure pointers burnus at gcc dot gnu dot org
2007-10-16 4:32 ` jv244 at cam dot ac dot uk
2007-10-16 6:46 ` burnus at gcc dot gnu dot org
2007-10-16 8:31 ` jv244 at cam dot ac dot uk
2007-10-16 11:26 ` burnus at gcc dot gnu dot org
2008-05-24 17:52 ` jaydub66 at gmail dot com
2008-05-25 12:14 ` jv244 at cam dot ac dot uk
2008-05-29 11:29 ` burnus at gcc dot gnu dot org
2008-06-02 15:33 ` burnus at gcc dot gnu dot org [this message]
2008-07-02 19:55 ` janus at gcc dot gnu dot org
2008-07-02 20:20 ` janus at gcc dot gnu dot org
2008-07-02 20:20 ` janus at gcc dot gnu dot org
2008-07-03 13:44 ` jv244 at cam dot ac dot uk
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=20080602153222.18803.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).