From: Aldy Hernandez <aldyh@redhat.com>
To: Kumar Gala <kumar.gala@motorola.com>
Cc: Zack Weinberg <zack@codesourcery.com>, <gcc@gcc.gnu.org>,
Jan Hubicka <jh@suse.cz>
Subject: Re: Branch created: gcc-3_3-e500-branch
Date: Wed, 16 Apr 2003 16:50:00 -0000 [thread overview]
Message-ID: <AAED50DA-7026-11D7-ACA8-000393750C1E@redhat.com> (raw)
In-Reply-To: <99D7A0CA-7023-11D7-B987-000393DBC2E8@motorola.com>
On Wednesday, April 16, 2003, at 11:53 AM, Kumar Gala wrote:
> What is left to submit / get working in the mainline w/respect to the
> ABI?
>
varargs are broken because of GCC infrastructure problems for subregs
of simd types on hard registers. I suggested an approach, but Jan
Hubicka had another idea which he hasn't implemented. I may kludge it
on the e500 branch, since there doesn't seem to be an agreement on how
to fix GCC.
long doubles are broken on purpose on mainline. The ABI specifies 128
bit long doubles, but I have left them as 64 bits since there are no
emulation bits for powerpc-eabi*.
vector types going on varargs, in the named section of the arguments,
are supposed to be split. They currently are not.
Everything above I'm "working on".
Finally, there are a mess of multilibs to be built by default. I have
a patch, but I'm still testing the multilibs before I commit to
mainline.
next prev parent reply other threads:[~2003-04-16 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 22:07 Zack Weinberg
2003-04-16 1:15 ` Kumar Gala
2003-04-16 1:16 ` Zack Weinberg
2003-04-16 9:25 ` Kumar Gala
2003-04-16 16:09 ` Aldy Hernandez
2003-04-16 16:15 ` Kumar Gala
2003-04-16 16:50 ` Aldy Hernandez [this message]
2003-04-16 22:19 ` Jan Hubicka
2003-04-17 4:54 ` Zack Weinberg
2003-04-17 16:46 ` Aldy Hernandez
2003-04-17 17:28 ` Zack Weinberg
2003-05-15 4:10 ` Kumar Gala
2003-05-15 4:38 ` Zack Weinberg
2003-05-15 14:41 ` Kumar Gala
2003-05-15 15:43 ` Mark Mitchell
2003-05-15 20:14 ` Geoff Keating
2003-05-15 14:45 ` altivec testsuite Kumar Gala
2003-04-16 14:14 ` Branch created: gcc-3_3-e500-branch Gerald Pfeifer
2003-04-16 17:16 ` Zack Weinberg
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=AAED50DA-7026-11D7-ACA8-000393750C1E@redhat.com \
--to=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=kumar.gala@motorola.com \
--cc=zack@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).