linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cal Erickson <cal_erickson@mvista.com>
To: Seong-kyu Ko <sugenius@doit.ajou.ac.kr>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problems of the corss-compiler.
Date: Mon, 28 Aug 2000 11:04:01 -0700	[thread overview]
Message-ID: <39AAA991.32FDF058@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.21.0008290209060.960-100000@doit.ajou.ac.kr


Seong-kyu,

In the MSR of the PPC processor there is a bit
that indicates whether there is hardware
floating point unit available. This bit should
be set in the state to turn hardware floating
point off when not present. In my experience
even on PowerPC cpus which have hardware
floating point some people do not need or
want to use it. So they make sure that the
MSR is set properly.

That being said, it is important to either make
sure that bit is always set properly or provide
the proper library routines to make sure that
you are getting the desired results. For instance,
the 8xx family of PPC does not have floating point
hardware. So you provide libraries that do
software floating point. The one area where
this comes into play is when using va_args in the
runtime of the C-library. It is typical to save the
registers and the floating point state upon
entry. If the routine does not check the MSR bit
and branch around the floating point state
save code then the system will crash as a
result of the floating point instructions. So the fix
is to eliminate that code from the library and not
depend on the state of the MSR bit. This makes
it necessary to have a special library for the 8xx
family of PPC processors.

Cal

Seong-kyu Ko wrote:

> Hi everyone.
> First, I'm sorry for my weak English.
>
> Well, Now I build a powerpc cross-compiler.
> so I compiled some binary using that cross-compiler, but
> I have some problems.
>
> I think cross-compiler is not problem.
> because I compile kernel with that cross-compiler, and
> kernel runs good.
>
> but, init, shell etc thease binaries have some problems.
> shell cant recieve argument, and some binaries print 'segmentation fault'
>
> I don't know why my compiler can't compile well.
>
> These are the packages that I used.
> 1. binutils-2.10
> 2. gcc-2.95.2
> 3. glibc-2.1.3 (add-ons : glibc-crypt-2.1, glibc-linuxthreads-2.1.3)
>
> First, I compile the binutils for powerpc cpu.
> Second, I build cross compiler with gcc.
> Third, I compile glibc for powerpc with cross compiler that I made.
> Last, I re-build cross compiler include glibc for library.
>
> Please tell me what do you think about that And why the problem happen.
> I'll wait your answers.
> thank you.
>

--
===========================================================================
Cal Erickson                 MontaVista Software Inc.
Customer Support Engineer    490 Potrero Avenue
Phone (408) 328-0304         Sunnyvale CA 94085
Fax   (408) 328-9204         e-mail cal_erickson@mvista.com
Pager 877-566-2012           support 1-800-759-8888 pin 202-7489
web http://www.mvista.com    support e-mail: support@mvista.com
eCode: http://cal@work.com.ecode.com
===========================================================================


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

  parent reply	other threads:[~2000-08-28 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-28 17:17 Problems of the corss-compiler Seong-kyu Ko
2000-08-28 17:25 ` Ralph Blach
2000-08-28 18:04 ` Cal Erickson [this message]
2000-08-28 19:34   ` Tom Roberts
2000-08-29  4:11   ` software floating point ÁֹαÔ
2000-08-29  4:48     ` Graham Stoney
  -- strict thread matches above, loose matches on Subject: below --
2000-08-28 17:38 Problems of the corss-compiler Whitney, John

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=39AAA991.32FDF058@mvista.com \
    --to=cal_erickson@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=sugenius@doit.ajou.ac.kr \
    /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).