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: Wed, 17 Jan 2007 16:58:00 -0000	[thread overview]
Message-ID: <20070117165829.28468.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30432-3107@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from sje at cup dot hp dot com  2007-01-17 16:58 -------
The code in comment #5 works fine.  In pure C cases, if a prototype has been
seen when you get to the call, the floating point value goes into a FP reg.  If
you haven't seen a prototype then the value goes into both an FP reg -and- a
general register. In the Fortran case the floating point value is only going
into a general register.  I think the only way to reproduce this in C is to
have a protype for the f_to_f function that looks like f_to_f (int, ...).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30432


  parent reply	other threads:[~2007-01-17 16:58 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
2007-01-14  5:28 ` pinskia at gcc dot gnu dot org
2007-01-17 16:58 ` sje at cup dot hp dot com [this message]
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=20070117165829.28468.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).