public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Kumar Gala <kumar.gala@motorola.com>,  <gcc@gcc.gnu.org>,
	Jan Hubicka <jh@suse.cz>
Subject: Re: Branch created: gcc-3_3-e500-branch
Date: Thu, 17 Apr 2003 04:54:00 -0000	[thread overview]
Message-ID: <87d6jlewlt.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <AAED50DA-7026-11D7-ACA8-000393750C1E@redhat.com> (Aldy Hernandez's message of "Wed, 16 Apr 2003 12:15:40 -0400")

Aldy Hernandez <aldyh@redhat.com> writes:

> 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.

Can I impose upon you to test and commit your future E500 patches both
on the mainline and on the new branch?  (Once I've got the backport
done.)  That way people using the branch automatically stay up to date.

zw

  parent reply	other threads:[~2003-04-17  1:33 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
2003-04-16 22:19             ` Jan Hubicka
2003-04-17  4:54             ` Zack Weinberg [this message]
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=87d6jlewlt.fsf@egil.codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=aldyh@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=kumar.gala@motorola.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).