From: Andrew Cagney <ac131313@ges.redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips-n32 reg_struct_has_addr
Date: Wed, 07 Aug 2002 10:12:00 -0000 [thread overview]
Message-ID: <3D5154ED.5080908@ges.redhat.com> (raw)
In-Reply-To: <3D504E8C.4C0FD7BE@redhat.com>
> No, I don't think this is right. As best I can tell, there is no cap on
>> the size of a struct that is passed by register.
>>
>> http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi/srch3@o32/0650/bks/SGI_Developer/books/Mpro_n32_ABI/sgi_html/ch02.html#id80931
>>
>> I.e., o32 and n32/n64 are the same -> never pass structures by reference.
>
>
> OK, patch withdrawn, I will resubmit it using this assumption,
> just to get the gdbarch-ification checked in, and then we can
> work on resolving how N32/64 should work.
Thanks!
BTW, if you're trying to test this, DO NOT TRUST GCC! Check things out
with an SGI compiler.
Andrew
prev parent reply other threads:[~2002-08-07 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 19:37 Michael Snyder
2002-08-06 15:02 ` Andrew Cagney
2002-08-06 15:50 ` Michael Snyder
2002-08-06 15:51 ` Michael Snyder
2002-08-07 10:12 ` Andrew Cagney [this message]
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=3D5154ED.5080908@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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