From: Andrew Cagney <ac131313@redhat.com>
To: Jason Thorpe <thorpej@wasabisystems.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa?] Implement ppc32 SYSV {extract,store} return value
Date: Fri, 10 Oct 2003 20:32:00 -0000 [thread overview]
Message-ID: <3F87176F.4050207@redhat.com> (raw)
In-Reply-To: <D38D50DF-FB5F-11D7-A35F-000A957650EC@wasabisystems.com>
>
> On Friday, October 10, 2003, at 01:22 PM, Andrew Cagney wrote:
>
> My apologies for not having a lot of time to keep up with this, but...
>
> + /* For NetBSD, this is an on again, off again thing. Some systems
> + do use the broken struct convention, and some don't. */
> set_gdbarch_use_struct_convention (gdbarch, ppcnbsd_use_struct_convention);
> + set_gdbarch_extract_return_value (gdbarch, ppc_sysv_abi_broken_extract_return_value);
> + set_gdbarch_store_return_value (gdbarch, ppc_sysv_abi_broken_store_return_value);
> set_solib_svr4_fetch_link_map_offsets (gdbarch,
> nbsd_ilp32_solib_svr4_fetch_link_map_offsets);
>
> on-again, off-again... which version of the compiler does which? Is this a bug in GCC 2.95.3 (which is what shipped with NetBSD 1.6)? (NetBSD 2.0 is going to ship with GCC 3.3.1.)
The GCC shipped in 1.5 vs the one now in 1.6
$ gcc --version
2.95.3
Andrew
next prev parent reply other threads:[~2003-10-10 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 21:54 Andrew Cagney
2003-09-22 21:58 ` Kevin Buettner
2003-10-04 17:43 ` Andrew Cagney
2003-10-06 19:12 ` Kevin Buettner
2003-10-10 20:22 ` Andrew Cagney
2003-10-10 20:25 ` Jason Thorpe
2003-10-10 20:32 ` Andrew Cagney [this message]
2003-10-10 20:34 ` Jason Thorpe
2003-10-10 21:01 ` Andrew Cagney
2003-10-10 21:00 ` Kevin Buettner
2003-10-10 21:27 ` 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=3F87176F.4050207@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=thorpej@wasabisystems.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