From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7874 invoked by alias); 12 Jan 2007 22:37:20 -0000 Received: (qmail 7812 invoked by uid 48); 12 Jan 2007 22:37:06 -0000 Date: Fri, 12 Jan 2007 22:37:00 -0000 Message-ID: <20070112223706.7811.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/30432] gfortran.dg/c_by_val_1.f fails on ia64-*-*, problem with %VAL In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "sje at cup dot hp dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-01/txt/msg01031.txt.bz2 ------- Comment #4 from sje at cup dot hp dot com 2007-01-12 22:37 ------- Here is a little more information: In the broken case (my small test case with the initial integer argument), when I call ia64_function_arg (via the FUNCTION_ARG macro) the named argument has a value of zero. This results in the floating point argument being put in an integer register. In the working case (no initial integer argument), named is one and the floating point argument gets put in a floating point register. I am not sure what triggers the different value for the named parameter though. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30432