This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [PATCH,fortran] fix iso_c_binding only clause bug
- From: "Tobias Burnus" <burnus at ph2 dot uni-koeln dot de>
- To: <crickett at lanl dot gov>, <fortran at gcc dot gnu dot org>
- Cc: <burnus at net-b dot de>
- Date: Wed, 4 Jul 2007 20:59:55 +0200 (CEST)
- Subject: Re: [PATCH,fortran] fix iso_c_binding only clause bug
Hi Chris,
> with this patch applied, the code snippet on the Fortran2003Bind_C wiki no
> longer reports the bogus errors it use to.
Thanks. Note that I want to phase out the wiki in favour of Bugzilla.
If you are looking for more C interoperability-related bugs:
[ISO C Binding] Accepts character with len /= 1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32599
This is something which should be rejected for -std=f2003; it should be
easy using "gfc_notify_std (GFC_STD_F2003, ..." I think one can allow it
by default, but I don't mind always rejecting it.Note: using "call foo("abcdef"//C_CHAR_NULL)" works with
"character(len=0),dimension(*)" per F2003 standard, which is implemented
in gfortran. Thus prohibiting it completely would also be ok.
[ISO Bind C] Access to private components not prevented
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32601
I don't care whether one allows it for -std=gnu or not. Allowing it (for
-std=gnu) is ok as one can use it for "print *" debugging. However, if one
wants to allow it, one should some testing to make sure one does not get
ICEs. The PR contains also an example which triggers an internal compiler
error.
Tobias
PS: Chris, I think you are involved in http://sourceforge.net/projects/ccain/
Does this work with gfortran's ISO Bind(C)? I wanted to try it but I
cannot get past configure:http://sourceforge.net/tracker/index.php?func=detail&aid=1747338&group_id=132751&atid=725219