From: Ian Lance Taylor <iant@google.com>
To: Reid M <reid3759@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: build libgcc for i486 with msoft-float failed
Date: Mon, 07 Oct 2013 15:54:00 -0000 [thread overview]
Message-ID: <CAKOQZ8ySW-mm0w2ab4yUarHd2ybjoF_0f66hD5KOqOvr9OAhfg@mail.gmail.com> (raw)
In-Reply-To: <CALe6A_-O=wV=qe=GeJbO+mPTCdg-1eDCTqG9avzWvnzrzp-EMg@mail.gmail.com>
On Sat, Oct 5, 2013 at 11:02 PM, Reid M <reid3759@gmail.com> wrote:
> I was trying to build cross gcc and libgcc based on gcc-4.8 for target
> i486 without floating point support.
Do you really have that hardware platform--80486 without 80487?
> 2. After I comment out the inline assembly to avoid error 1, I could
> get a libgcc for i486 version. There's some undefined soft-float
> function as the following. The source code of corresponding function
> are existed in libgcc but they aren't included in libgcc.a.
> out/target/product/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a(time.o):
> In function `clock_now':
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__floatsidf'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__floatsidf'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__muldf3'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__adddf3'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__fixdfsi'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__floatsidf'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__floatsidf'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__muldf3'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__adddf3'
> /home/reid/android/android-4.2.1_r1/bionic/libc/unistd/time.c:53:
> undefined reference to `__fixdfsi
You should try adding t-softfp to tmake_file in config.host. I don't
know if that is all you will need but it will take you one step
further. See the targets in config.host that use t-softfp. Note that
you don't want i386/t-softfp, or at least not just that--that is just
an RTEMS patch and doesn't do most of what is needed.
Ian
next prev parent reply other threads:[~2013-10-07 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 6:02 Reid M
2013-10-06 17:33 ` Kai Ruottu
2013-10-07 15:54 ` Ian Lance Taylor [this message]
2013-10-07 18:43 ` Reid M
2013-11-05 18:41 Uros Bizjak
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=CAKOQZ8ySW-mm0w2ab4yUarHd2ybjoF_0f66hD5KOqOvr9OAhfg@mail.gmail.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=reid3759@gmail.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).