Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: David B Anderson <davea@quasar.engr.sgi.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [rfa] mips argument passing fixes for o32
Date: Sun, 15 Jul 2001 15:22:00 -0000	[thread overview]
Message-ID: <20010715152239.A21579@nevyn.them.org> (raw)
In-Reply-To: <3B521018.5080706@cygnus.com>

On Sun, Jul 15, 2001 at 05:50:16PM -0400, Andrew Cagney wrote:
> You wouldn't have access to such a machine by any chance? :-)
> 
> I'm getting the feeling I'm wrong with this one - for some strange 
> historical reason LE o32 really does left/right shift small parameters 
> (I'm still mining the archives).
> 
> Assuming that is the case ...
> 
> >  if (!MIPS_EABI
> >  		      && MIPS_SAVED_REGSIZE < 8
> > -		      && TARGET_BYTE_ORDER == BIG_ENDIAN
> > +		      && (TARGET_BYTE_ORDER == BIG_ENDIAN
> > +			  || TYPE_LENGTH (arg_type) < MIPS_SAVED_REGSIZE)
> >  		      && partial_len < MIPS_SAVED_REGSIZE
> >  		      && (typecode == TYPE_CODE_STRUCT ||
> >  			  typecode == TYPE_CODE_UNION))
> 
> I don't know that line being added should be
> 
> 	
> 
> || TYPE_LENGTH (arg_type) < MIPS_SAVED_REGSIZE
> 
> 
> it should at least be guarded by ``ABI == o32''.  What does LE n32 do 
> for instance?
> If GCC, for o32, always left shifts the structs dregs (PARTIAL_LEN < 
> MIPS_SAVED_REGSIZE) then is just the ABI test needed?

That's not what it does, though.  It only left-shifts the dregs if they
constitute the entire structure; thus the check I used.  Little-endian
will left-shift only small structs, while big-endian will left-shift
small structs or leftovers.

As for when it is done, GCC says:
      if (struct_p && int_size_in_bytes (type) < UNITS_PER_WORD
          && ! TARGET_64BIT && mips_abi != ABI_EABI)

However, there's a comment to the effect that the !TARGET_64BIT is
actually wrong, and being used only for efficiency.  So I'm not sure
precisely when this applies.  It seems that !MIPS_EABI and
MIPS_SAVED_REGSIZE < 8 would agree with at least the way that GCC does
things, but GCC is not a sterling example of n32 or n64 compatibility.

> PS: That function is the official example of how to _not_ multi-arch an ABI.

And does it ever show...

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-07-15 15:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12 17:03 David B Anderson
2001-07-15 14:50 ` Andrew Cagney
2001-07-15 15:22   ` Daniel Jacobowitz [this message]
2001-07-16  7:46     ` Andrew Cagney
2001-07-15 20:29 ` David B Anderson
2001-07-16 16:44   ` Andrew Cagney
2001-07-17  7:49   ` David B Anderson
2001-07-18 13:29     ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2001-07-06 11:26 Daniel Jacobowitz
2001-07-06 14:24 ` Andrew Cagney
2001-07-12  0:47 ` Andrew Cagney
2001-07-12 10:35   ` Daniel Jacobowitz
2001-07-12  1:23 ` Andrew Cagney
2001-07-12 10:39   ` Daniel Jacobowitz
2001-07-12 11:59     ` Andrew Cagney
2001-07-12 12:21       ` Daniel Jacobowitz
2001-07-12 12:38         ` Andrew Cagney
     [not found]       ` <3B58AEBE.1000304@cygnus.com>
     [not found]         ` <20010720152547.A10028@nevyn.them.org>
2001-07-20 16:35           ` Andrew Cagney
2001-07-20 16:46             ` Elena Zannoni
2001-07-23 20:36               ` Andrew Cagney
2001-11-14 14:15         ` Daniel Jacobowitz
2001-11-27  7:48           ` Daniel Jacobowitz

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=20010715152239.A21579@nevyn.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=ac131313@cygnus.com \
    --cc=davea@quasar.engr.sgi.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