From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Mips, return_value_location, small structs
Date: Fri, 09 Aug 2002 17:37:00 -0000 [thread overview]
Message-ID: <3D545BC7.B41142D4@redhat.com> (raw)
In-Reply-To: <3D545AB2.4030803@ges.redhat.com>
Andrew Cagney wrote:
>
> > Re-submitted as a separate patch.
> >
> > The problem: small structs returned in one (or two) registers
> > are aligned left in N32/N64 and aligned right in the others
> > (or vice versa, depending on how you cross your eyes).
>
> I _think_ you also need to add o32. Can you check that out? Just post
> the results, not the patch.
I know o32 needs work too, but the two can be treated separately.
I do guarantee that this patch does not make o32 any worse.
In fact, I have been testing to make sure that none of my patches
have made o32 any worse.
Can I check this one in for n32, if I promise to work on o32 next?
>
> Andrew
>
> > There are two code paths here, one for structs of length < MIPS_REGSIZE,
> > and one for MIPS_REGSIZE < struct len < 2 * MIPS_REGSIZE.
> >
> > The first case I've split into two paths: one for N32 &&
> > TYPE_CODE_STRUCT,
> > and a second for everything else (the later being identical to what was
> > there before).
> >
> > In the second case, I've simply let the N32/N64 path fall thru.
> > The next "if" catches it and handles it correctly.
> >
> >
> >
> > 2002-08-08 Michael Snyder <msnyder@redhat.com>
> >
> > * mips-tdep.c (return_value_location): Structs returned in
> > registers are aligned differently (n32/64 vs. o32/64).
> >
> > Index: mips-tdep.c
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/mips-tdep.c,v
> > retrieving revision 1.92
> > diff -c -3 -p -r1.92 mips-tdep.c
> > *** mips-tdep.c 8 Aug 2002 00:26:51 -0000 1.92
> > --- mips-tdep.c 8 Aug 2002 21:48:09 -0000
> > *************** return_value_location (struct type *valt
> > *** 3608,3622 ****
> > if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG
> > && len < MIPS_SAVED_REGSIZE)
> > {
> > ! /* "un-left-justify" the value in the low register */
> > ! lo->reg_offset = MIPS_SAVED_REGSIZE - len;
> > ! lo->len = len;
> > hi->reg_offset = 0;
> > hi->len = 0;
> > }
> > else if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG
> > && len > MIPS_SAVED_REGSIZE /* odd-size structs */
> > && len < MIPS_SAVED_REGSIZE * 2
> > && (TYPE_CODE (valtype) == TYPE_CODE_STRUCT ||
> > TYPE_CODE (valtype) == TYPE_CODE_UNION))
> > {
> > --- 3608,3635 ----
> > if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG
> > && len < MIPS_SAVED_REGSIZE)
> > {
> > ! if ((gdbarch_tdep (current_gdbarch) -> mips_abi == MIPS_ABI_N32
> > ! || gdbarch_tdep (current_gdbarch) -> mips_abi == MIPS_ABI_N64)
> > ! && (TYPE_CODE (valtype) == TYPE_CODE_STRUCT
> > ! || TYPE_CODE (valtype) == TYPE_CODE_UNION))
> > ! {
> > ! /* Values are already aligned in the low register. */
> > ! lo->reg_offset = 0;
> > ! }
> > ! else
> > ! {
> > ! /* "un-left-justify" the value in the low register */
> > ! lo->reg_offset = MIPS_SAVED_REGSIZE - len;
> > ! }
> > hi->reg_offset = 0;
> > + lo->len = len;
> > hi->len = 0;
> > }
> > else if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG
> > && len > MIPS_SAVED_REGSIZE /* odd-size structs */
> > && len < MIPS_SAVED_REGSIZE * 2
> > + && gdbarch_tdep (current_gdbarch) -> mips_abi != MIPS_ABI_N32
> > + && gdbarch_tdep (current_gdbarch) -> mips_abi != MIPS_ABI_N64
> > && (TYPE_CODE (valtype) == TYPE_CODE_STRUCT ||
> > TYPE_CODE (valtype) == TYPE_CODE_UNION))
> > {
next prev parent reply other threads:[~2002-08-10 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 15:07 Michael Snyder
2002-08-09 17:13 ` Andrew Cagney
2002-08-09 17:37 ` Michael Snyder [this message]
2002-08-09 19:39 ` Andrew Cagney
2002-08-12 11:50 ` Michael Snyder
2002-08-14 12:23 ` Michael Snyder
2002-08-16 10:58 ` Andrew Cagney
2002-08-19 14:39 ` Andrew Cagney
2002-08-20 11:49 ` Michael Snyder
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=3D545BC7.B41142D4@redhat.com \
--to=msnyder@redhat.com \
--cc=ac131313@ges.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