linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: David Edelsohn <dje@watson.ibm.com>,
	linuxppc-dev@lists.linuxppc.org,
	yellowdog-devel@lists.terrasoftsolutions.com
Subject: Re: Status of 2.5.X kernels on PPC Linux, anyone working with NPTL?
Date: Sun, 3 Nov 2002 10:55:09 -0800	[thread overview]
Message-ID: <20021103185509.GA2437@redhat.com> (raw)
In-Reply-To: <66242FA2-EF5C-11D6-81A1-0003938E434C@ivey.uwo.ca>


On Sun, Nov 03, 2002 at 01:45:18PM -0500, Kevin B. Hendricks wrote:
> Hi,
>
> >I also vaguely recall that Geoff has a list of ABI changes pending.
> >Perhaps we should do all these at the same time.
> >
> Current violations of the abi for ppc linux include:
>
> - missing support for small structure return values in register pairs
> r3, r4

I thought support for this already in place, but gcc had the wrong
endianness in the registers.  If this is so, I already have a patch
for this (not commited though ;-)).

> think about a
> simultaneous push of patches to many of these projects to help them
> maintain
> support for ppc linux.

But but... I've been hacking gcc so long, I can only write in K&R :-).

Aldy

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-11-03 18:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 15:12 Status of 2.5.X kernels on PPC Linux, anyone working with NPTL? Kevin Hendricks
2002-10-09 16:34 ` David Edelsohn
2002-10-09 17:14   ` Kevin Hendricks
2002-11-03 18:28   ` Aldy Hernandez
2002-11-03 18:45     ` Kevin B. Hendricks
2002-11-03 18:55       ` Aldy Hernandez [this message]
2002-11-03 20:06         ` Kevin B. Hendricks
2002-10-10  2:26 ` Tom Rini
2002-10-27 12:30 ` Giuliano Pochini

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=20021103185509.GA2437@redhat.com \
    --to=aldyh@redhat.com \
    --cc=dje@watson.ibm.com \
    --cc=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-devel@lists.terrasoftsolutions.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 NNTP newsgroup(s).