Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] sh-tdep.c: Fix float handling
Date: Fri, 10 Oct 2003 19:22:00 -0000	[thread overview]
Message-ID: <20031010192252.GQ14344@cygbert.vinschen.de> (raw)
In-Reply-To: <16263.30.584298.427986@localhost.redhat.com>

On Fri, Oct 10, 2003 at 02:53:18PM -0400, Elena Zannoni wrote:
> Please add this expanation as a comment. I find cleared than your
> shorter comments. Just add it before the helper function.
> 
> >From here....
> 
>  > First, in contrast to non-FPU CPUs, arguments are never split between
>  > registers and stack.  If an argument doesn't fit in the remaining registers
>  > it's always pushed entirely on the stack.  My testing led me to the wrong
>  > assumption that just types > 16 bytes are pushed entirely on the stack.

I have a problem with this first part of the comment.  This one does
not fit well as a comment to the helper function.  I would suggest to
add this (carefully rephrased) to sh_push_dummy_call_fpu(), substituting
the very short

  /* No data is passed partially in registers.  */

comment instead.  Ok?

> Since this is a predicate, can you call it sh_treat_as_flt_p .

Ok.

> Ok otherwise.

Thanks, I'd just like to hear about the above comment.

> BTW, what multilibs are you testing?

Several, -m2, -m2e, m3e, m4, m4 -ml, -m4-single.

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.


  reply	other threads:[~2003-10-10 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04 12:11 Corinna Vinschen
2003-10-10 18:42 ` Elena Zannoni
2003-10-10 19:22   ` Corinna Vinschen [this message]
2003-10-10 20:14     ` Elena Zannoni
2003-10-10 20:33       ` Corinna Vinschen

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=20031010192252.GQ14344@cygbert.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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