public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57048] [4.9 Regression] Handling of C_PTR and C_FUNPTR leads to reject valid
Date: Sat, 23 Nov 2013 13:33:00 -0000 [thread overview]
Message-ID: <bug-57048-4-gPmk3hP60Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57048-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57048
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-11-23
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
On x86_64-apple-darwin13, I get with gfortran 4.8.2
[Book15] f90/bug% gfortran pr57048.f90
[Book15] f90/bug% grep funptr m.mod
(('c_funptr' '__iso_c_binding' 2) ('t' 'm' 3))
(2 'C_funptr' '__iso_c_binding' '' 1 ((DERIVED UNKNOWN-INTENT
DERIVED 2 0 1 1 UNKNOWN ()) 0 0 () () 0 ((4 '__c_funptr_c_address' (
(UNKNOWN 0 0 0 0 UNKNOWN ()) 0 0 () () 0 ((5 'funptr' (DERIVED 2 0 0 0
7 'c_funptr' '__iso_c_binding' '' 1 ((PROCEDURE UNKNOWN-INTENT
('C_funptr' 0 2 'T' 0 3 '__iso_c_binding' 0 6 'c_funptr' 0 7 'm' 0 8 't'
What is setting the capital C and why?
next prev parent reply other threads:[~2013-11-23 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 13:02 [Bug fortran/57048] New: " burnus at gcc dot gnu.org
2013-04-23 13:02 ` [Bug fortran/57048] " burnus at gcc dot gnu.org
2013-10-30 11:38 ` rguenth at gcc dot gnu.org
2013-11-23 13:33 ` dominiq at lps dot ens.fr [this message]
2014-01-26 17:21 ` mikael at gcc dot gnu.org
2014-01-26 17:23 ` mikael at gcc dot gnu.org
2014-04-22 11:37 ` [Bug fortran/57048] [4.9/4.10 " jakub at gcc dot gnu.org
2014-07-16 13:31 ` jakub at gcc dot gnu.org
2014-10-30 10:42 ` [Bug fortran/57048] [4.9/5 " jakub at gcc dot gnu.org
2015-06-26 20:09 ` [Bug fortran/57048] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:35 ` jakub 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-57048-4-gPmk3hP60Y@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).