From: Joel Brobecker <brobecker@adacore.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix passing double float complex arguments in sparc64
Date: Tue, 11 Feb 2014 04:45:00 -0000 [thread overview]
Message-ID: <20140211044530.GJ5485@adacore.com> (raw)
In-Reply-To: <87bnyfgkw4.fsf@oracle.com>
> Somehow I missed the fact that for big structs and unions the writing of
> the "additional" register is performed immediately after setting regnum.
> A bit confusing, but that avoids repeated logic in the `if (regnum !=
> 1)' block, so I agree it is a better solution.
Thank you. I don't think one way is all that better than the other
(I actually find this way a little confusing at first), but I prefer
that everything remains consistent...
> n2013-10-15 Jose E. Marchesi <jose.marchesi@oracle.com>
>
> * sparc64-tdep.c (sparc64_store_arguments): Do not align complex
> double float arguments to 16-byte in the argument slots.
The patch is OK. Watch out for the 'n' at the start of the date in
this ChangeLog entry.
Just one tiny formatting request before committing:
> + /* Float Complex or double Complex arguments. */
> + if (element < 16)
> + {
> + regnum = SPARC64_D0_REGNUM + element;
> +
> + if (len == 16)
Can you remove the tabs/spaces in the empty line before the "if"?
Thank you,
--
Joel
next prev parent reply other threads:[~2014-02-11 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 15:01 Jose E. Marchesi
2014-02-05 19:02 ` Jose E. Marchesi
2014-02-08 2:47 ` Joel Brobecker
2014-02-10 13:22 ` Jose E. Marchesi
2014-02-11 4:45 ` Joel Brobecker [this message]
2014-02-11 12:39 ` Jose E. Marchesi
-- strict thread matches above, loose matches on Subject: below --
2013-10-15 15:55 Jose E. Marchesi
2013-10-23 19:58 ` Mark Kettenis
2013-12-10 18:46 ` Jose E. Marchesi
2013-12-11 12:29 ` Jose E. Marchesi
2013-12-11 14:09 ` Jose E. Marchesi
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=20140211044530.GJ5485@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.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