linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brendan Simon <bsimon@ctam.com.au>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: glibc for mpc860
Date: Fri, 10 Sep 1999 16:37:54 +1000	[thread overview]
Message-ID: <37D8A742.6550860E@ctam.com.au> (raw)
In-Reply-To: 37D88E48.23A1728C@jlc.net


Dan Malek wrote:

> Brendan Simon wrote:
>
> > ... I dowloaded the latest glibc (2.1.1) from a GNU mirror
> > and it compiled fine with my egcs-1.1.2 powerpc-linux cross-compiler.  I
> > tried adding the -mcpu=860 option and it barfed.
>
> I still use the old libc-1.99 stuff.  I have not looked into
> using the newer glibc2.  I don't use cross compilers because of
> problems others have had.  That could be some of the problem
> as well.

I just downloaded the tar.gz archive from the LinuxPPC ftp site.  It has the libaries but not the source.  I thought at least
the headers would be in there but it doesn't look like it.
Excuse my ignorance but is the libc-1.99 stuff a GNU product ?

I assume by the statement "I don't use cross compilers" means that you use the native compiler on a LinuxPPC machine (powermac
or something).  This would mean that the instructions generated are for 601, 603 or whatever the default is.  This would surely
cause problems on an MPC860 processor wouln't it ?


> > ..... I assume that the glibc
> > developers do not consider targets without a floating point processor as
> > a non-priority (I wish the MPC860 had an FPU).
>
> It seems anything that is not the latest and fastest silicon is
> a non-priority :-).  I had the patches for the libraries in the
> past....no one was interested.  If you really need an FPU, you
> should probably be using something other than an 8xx.  I have done
> lots of cool 8xx applications, mostly communications related.
> I have never needed an FPU.

I don't have a NEED for an FPU for most projects but I still wish it was available.  There aren't too many CPUs these days that
don't have one built in (except for 8, 16 and some embedded 32 bit processors).  A lot of software these days assumes that an
FPU is present (eg. glibc by the looks of it).  It would be nice to have an FPU just incase it was useful.  I'm sure it wouldn't
cost Motorola much to put it on.  It's just a wish.  Sigh...  I thought the MPC8260 would have an FPU but it appears not.  Ah
well.


> > ......It looks like others
> > have ported/modified some glibc sources to work with the -mcpu=860
> > option.
>
> You shouldn't have to modify anything in the sources to get it
> to compile.  The hardest part is getting the flags in the Makefiles.

I think I used something like "CC=powerpc-linux CFLAGS=-mcpu=860 configure" when I tried compiling glibc.  The -mcpu=860 flag
was present in the commands generated by Make which caused the glibc build to die.  Maybe there is something like -msoft or -nfp
that I can try ?


> I attached the single file to be modified for the cache line stuff
> in the older glibc-1.99 sources.  You can also remove the floating
> point instructions in the set/long jump function, but it is not
> necessary.  Those are the only floating point instructions in
> the libraries.

I'll have a look.

Thanks,
Brendan Simon.


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

  parent reply	other threads:[~1999-09-10  6:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-10  0:41 glibc for mpc860 Brendan Simon
     [not found] ` <37D88E48.23A1728C@jlc.net>
1999-09-10  6:37   ` Brendan Simon [this message]
1999-09-10 10:08 ` Marcus Sundberg
1999-09-10 11:57   ` Kenneth Johansson
1999-09-13  2:37     ` Brendan Simon
1999-09-13  4:45       ` Dan Malek

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=37D8A742.6550860E@ctam.com.au \
    --to=bsimon@ctam.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).