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 21:01:00 -0000 [thread overview]
Message-ID: <3F871E28.8050607@redhat.com> (raw)
In-Reply-To: <1B04AB74-FB61-11D7-A35F-000A957650EC@wasabisystems.com>
> On Friday, October 10, 2003, at 01:32 PM, Andrew Cagney wrote:
>
> The GCC shipped in 1.5 vs the one now in 1.6
> $ gcc --version
> 2.95.3
>
> So, which one was right? The 1.5 compiler or the 1.6 compiler?
Neither, but from memory 1.5 was slightly closer:
> /* NetBSD is confused. It appears that 1.5 was using the correct SVr4
> convention but, 1.6 switched to the below broken convention. For
> the moment use the broken convention. Ulgh!. */
>
> static int
> ppcnbsd_use_struct_convention (int gcc_p, struct type *value_type)
> {
> if ((TYPE_LENGTH (value_type) == 16 || TYPE_LENGTH (value_type) == 8)
> && TYPE_VECTOR (value_type))
> return 0;
>
> return !(TYPE_LENGTH (value_type) == 1
> || TYPE_LENGTH (value_type) == 2
> || TYPE_LENGTH (value_type) == 4
> || TYPE_LENGTH (value_type) == 8);
> }
however, then GCC was getting:
+ /* GCC screwed up. The last register isn't "left" aligned.
+ Need to extract the least significant part of each
+ register and then store that. */
wrong.
Andrew
next prev parent reply other threads:[~2003-10-10 21:01 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
2003-10-10 20:34 ` Jason Thorpe
2003-10-10 21:01 ` Andrew Cagney [this message]
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=3F871E28.8050607@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