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: Wed, 14 Aug 2002 12:23:00 -0000 [thread overview]
Message-ID: <3D5AA9BC.3580169B@redhat.com> (raw)
In-Reply-To: <3D547CE2.6070403@ges.redhat.com>
Andrew Cagney wrote:
>
> > 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?
>
> Why not just fix this bug for all three ABIs? o32 is just like n32/n64
> in that it cross-eyes the arguments.
Andrew, o32 works as it is. I can't find anything related to this
patch that still needs to be done for o32. Unles you can suggest
something specific, may I check this patch in?
Michael
next prev parent reply other threads:[~2002-08-14 19:23 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
2002-08-09 19:39 ` Andrew Cagney
2002-08-12 11:50 ` Michael Snyder
2002-08-14 12:23 ` Michael Snyder [this message]
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=3D5AA9BC.3580169B@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