public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30432] gfortran.dg/c_by_val_1.f fails on ia64-*-*, problem with %VAL
Date: Fri, 12 Jan 2007 22:37:00 -0000 [thread overview]
Message-ID: <20070112223706.7811.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30432-3107@http.gcc.gnu.org/bugzilla/>
------- 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
next prev parent reply other threads:[~2007-01-12 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 0:10 [Bug fortran/30432] New: " sje at cup dot hp dot com
2007-01-12 21:00 ` [Bug fortran/30432] " pault at gcc dot gnu dot org
2007-01-12 21:52 ` sje at cup dot hp dot com
2007-01-12 21:54 ` sje at cup dot hp dot com
2007-01-12 22:37 ` sje at cup dot hp dot com [this message]
2007-01-14 5:28 ` pinskia at gcc dot gnu dot org
2007-01-17 16:58 ` sje at cup dot hp dot com
2007-01-22 22:46 ` sje at cup dot hp dot com
2007-01-30 17:49 ` sje at gcc dot gnu dot org
2007-02-01 12:28 ` [Bug fortran/30432] [4.2/4.1 only] " fxcoudert at gcc dot gnu dot org
2007-02-05 21:29 ` sje at gcc dot gnu dot org
2007-02-06 18:01 ` [Bug fortran/30432] [4.1 " sje at cup dot hp dot com
2007-02-06 23:18 ` fxcoudert at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070112223706.7811.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).