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 20:33:00 -0000 [thread overview]
Message-ID: <20031010203316.GR14344@cygbert.vinschen.de> (raw)
In-Reply-To: <16263.5574.385852.935704@localhost.redhat.com>
On Fri, Oct 10, 2003 at 04:25:42PM -0400, Elena Zannoni wrote:
> Corinna Vinschen writes:
> > > > 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. */
> >
>
> Where is that? I think you can add it before the function
> sh_push_dummy_call_fpu. Or where it makes more sense. I don't care, as
> long as the whole thing is as clear as possible. It is wasy to
> understand the code now, but I bet a few months from now we will all
> have forgotten the details.
I've applied this with the comment at the point I think it fit most well.
I agree to what you're saying, therefore I'm always trying to put some
additional comments in.
The above comment is now inline, beginnig at line 890 in
sh_push_dummy_call_fpu(), exactly above the code which cares for this
very situation.
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
prev parent reply other threads:[~2003-10-10 20:33 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
2003-10-10 20:14 ` Elena Zannoni
2003-10-10 20:33 ` Corinna Vinschen [this message]
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=20031010203316.GR14344@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