From: Daniel Jacobowitz <drow@false.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/CRIS] Prologue scan bug fixes, return_value implementation
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040303164450.GA18032@nevyn.them.org> (raw)
Message-ID: <20040319000900.BzTslYpHMC5nG6dwDbWrqt-2uMO0l8YDEbVJz_Ik0gM@z> (raw)
In-Reply-To: <40460A69.2060600@axis.com>
On Wed, Mar 03, 2004 at 05:40:09PM +0100, Orjan Friberg wrote:
> The patch below improves the CRIS prologue scanner by, at least partially,
> handling the case when the PC is still in the prologue, which takes care of
> 14 FAILs in recurse.exp and 2 FAILs in step-test.exp. I've also added a
> return_value implementation which gets rid of 32 FAILs and 30 KFAILs in
> structs.exp. (All tests in those test cases now PASS.)
>
> Ok to commit to trunk and 6.1 branch?
As Andrew mentioned, you're the listed maintainer of the CRIS port -
you don't need approval for changes to CRIS-specific files. I think
that at this point it's appropriate for the branch also.
> +/* Handle the CRIS return value convention. */
> +
> +static enum return_value_convention
> +cris_return_value (struct gdbarch *gdbarch, struct type *type,
> + struct regcache *regcache, void *readbuf,
> + const void *writebuf)
> +{
> + if (TYPE_CODE (type) == TYPE_CODE_STRUCT ||
> + TYPE_CODE (type) == TYPE_CODE_UNION ||
> + TYPE_LENGTH (type) > 8)
Style nit: || at the beginning of the line, please.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-03 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Orjan Friberg
2004-03-03 16:40 ` Orjan Friberg
2004-03-03 16:44 ` Daniel Jacobowitz [this message]
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Orjan Friberg
2004-03-03 16:59 ` Orjan Friberg
2004-03-19 0:09 ` Andrew Cagney
2004-03-03 18:47 ` Andrew Cagney
2004-03-04 9:23 ` Orjan Friberg
2004-03-19 0:09 ` Orjan Friberg
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=20040303164450.GA18032@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=orjan.friberg@axis.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