This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
thanks. Chris
i've updated the gen_cptr_param function and now gfortran reports the following for your code:
kargl_1.f03:2.42:
use iso_c_binding, only: c_f_procpointer 1 Error: Type 'C_FUNPTR' required for ISO_C_BINDING function at (1) kargl_1.f03:2.42:
use iso_c_binding, only: c_f_procpointer
1
Error: The derived type 'cptr' at (1) is of type 'c_funptr', which has not been defined
acceptable? if so, i'll apply it to trunk and bootstrap, regtest, and submit.
thanks. Chris
On Mon, 2 Jul 2007, Steve Kargl wrote:
On Mon, Jul 02, 2007 at 10:57:48AM -0600, Christopher D. Rickett wrote:i would also like to say thanks to all those who've helped me get this patch finished by helping with testing, cleanup, debugging, etc.
Chris
You have your first bug report. :-)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32579
It seems kind of odd to me that someone would use only C_F_PROCPOINTER in a module when its first argument is of type C_PTR. But, I checked Section 15 and could not find anything that says that C_PTR is a constraint on C_F_PROCPOINTER.
MODULE X USE ISO_C_BINDING, ONLY : C_F_PROCPOINTER END MODULE X
troutmask:kargl[207] ~/../sgk/work/4x/bin/gfortran -c a.f90 a.f90:2.43:
USE ISO_C_BINDING, ONLY : C_F_PROCPOINTER 1 Error: Type 'C_PTR' required for ISO_C_BINDING function at (1) a.f90:2.43:
USE ISO_C_BINDING, ONLY : C_F_PROCPOINTER
1
Error: The derived type 'cptr' at (1) is of type 'c_ptr', which has not been defined
-- Steve
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |