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: gdb-patches@sources.redhat.com
Subject: Re: [rfa] mips argument passing fixes for o32
Date: Thu, 12 Jul 2001 12:21:00 -0000	[thread overview]
Message-ID: <20010712122114.B25739@nevyn.them.org> (raw)
In-Reply-To: <3B4DF3A9.8010205@cygnus.com>

On Thu, Jul 12, 2001 at 02:59:53PM -0400, Andrew Cagney wrote:
> The SGI compilers are big endian (correct?) so who knows what they would 
> do in the little endian case.

There are other MIPS little-endian compilers, and:

> > The testcase was the passing of a three_char_t in call-ar-st (calling
> > print_three_chars from the gdb prompt).
> 
> 
> This is going to take more digging.  It smells like a GCC bug.  It is 
> definitly inconsistent with other ABIs where the struct is always stored 
> at A and not A+3.

If you read the original message at:
 < http://sources.redhat.com/ml/gdb-patches/2001-07/msg00156.html >
you'll see the comment in GCC about this behavior.  It says that
structures of less than word size will be passed in the high end of
registers, as a hack for compatibility with other MIPS compilers.

It would be interesting to see how other compilers actually handle
this, but I don't have access to any other little-endian MIPS
toolchains.

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


  reply	other threads:[~2001-07-12 12:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2001-07-12 17:03 David B Anderson
2001-07-15 14:50 ` Andrew Cagney
2001-07-15 15:22   ` Daniel Jacobowitz
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

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=20010712122114.B25739@nevyn.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=ac131313@cygnus.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