This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/30432] gfortran.dg/c_by_val_1.f fails on ia64-*-*, problem with %VAL
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Jan 2007 05:28:22 -0000
- Subject: [Bug fortran/30432] gfortran.dg/c_by_val_1.f fails on ia64-*-*, problem with %VAL
- References: <bug-30432-3107@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from pinskia at gcc dot gnu dot org 2007-01-14 05:28 -------
Hmmm, I wonder if ia64 is broken for the following C case:
TU1.c:
int f();
int g(int a, double c, int d)
{
return f(a, d);
}
TU2.c:
int f(int a, double b)
{
return b;
}
the named agrument is defined by:
current_function_stdarg
= (fntype
&& TYPE_ARG_TYPES (fntype) != 0
&& (TREE_VALUE (tree_last (TYPE_ARG_TYPES (fntype)))
!= void_type_node));
But I wonder if we get it even more incorrect someother cases too.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30432