This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC 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]

[Bug fortran/30432] gfortran.dg/c_by_val_1.f fails on ia64-*-*, problem with %VAL


------- Comment #7 from sje at cup dot hp dot com  2007-01-22 22:45 -------
So I can see things going wrong in expand_call but I still don't know why. 
With the FORTRAN example (comment #3) expand_call sets num_actuals to 2 and
n_named_args to 1.  If I write the calling code in C, num_actuals is 2 and
n_named_args is 3.  Because (in FORTRAN) num_actuals > n_named_args, I pass the
floating point value in a general register (like varags) instead of in a
floating point register like when I have a regular named argument.

n_named_args seems to be set based on list_length(type_arg_types) and for some
reason this is 3 for C and 1 for Fortran.  I think the fortran type_arg_types
list is wrong but I don't know why it is wrong.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30432
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]