This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PowerPC E500 hardware floating point support in libc


--- On Thu, 6/26/08, Joseph S. Myers <joseph@codesourcery.com> wrote:

> From: Joseph S. Myers <joseph@codesourcery.com>
> Subject: Re: PowerPC E500 hardware floating point support in libc
> To: "Alex Dubov" <oakad@yahoo.com>
> Cc: libc-ports@sourceware.org
> Date: Thursday, June 26, 2008, 4:34 AM
> On Wed, 25 Jun 2008, Alex Dubov wrote:
> 
> > I'm interested in having a hardware floating point
> working on 8548. I see,
> > there was a discussion couple of months back, but no
> consensus was reached,
> > as far as I can tell.
> > 
> > Basically, I want to implement the missing bits in
> libc (if there are 
> > any), but I would like to do it in a way that'll
> be acceptable for 
> > inclusion into the main tree.
> > 
> > I would also like to ask: what is the status of the
> already proposed 
> > patches? Are they usable for real projects or
> additional work is 
> > required?
> 
> First, if you wish to implement any patches, you should
> first make sure 
> you have a copyright assignment and any employer disclaimer
> needed on file 
> with the FSF before doing any work.
> 
> The patch as posted last September and discussed last
> October should still 
> work fine, *except* that core libc now has a file 
> sysdeps/unix/sysv/linux/powerpc/bits/mathinline.h that
> would need an extra 
> __NO_FPRS__ check similar to those in the libc part of my
> previous patch 
> submission.  You can find the relevant patch
> 
> 2008-04-12  Joseph Myers  <joseph@codesourcery.com>
> 
>         *
> sysdeps/unix/sysv/linux/powerpc/bits/mathinline.h: Also
> test
>         __NO_FPRS__.
> 
> in EGLIBC.  As the port is available to E500 users and
> subject to ongoing 
> automatic testing in EGLIBC, the FSF GLIBC submission is a
> low priority 
> for me.  The port has been working fine for over a year.
> 

Thank you for extended reply. As you can guess, I was not aware of eglibc existence until today.

I tried to follow your instructions from the eglibc website, trying different combinations of normal gcc (and sourcerygxx), as well as different branches of eglibc. Invariably, I get build errors in the eglibc or gcc (depending on the patches I apply).

Is there a "known good" combination of gcc and eglibc I can build to get started?



      


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]