From: "marty fouts" <mf.danger@gmail.com>
To: Niklaus <niklaus@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: need help with gcc 4.1.0 crosscompiler for arm
Date: Fri, 14 Apr 2006 05:07:00 -0000 [thread overview]
Message-ID: <9f7850090604132207u4e4040cvc279877865737346@mail.gmail.com> (raw)
In-Reply-To: <85e0e3140604132153v4c640b9dx3b0f67cf050c957e@mail.gmail.com>
On 4/13/06, Niklaus <niklaus@gmail.com> wrote:
[much snippage]
> > Basically, if I tell arm-elf-gcc which arm processor I'm using, it
> > recognizes that the processor has no floating point, so arm-elf-ld
> > fails, as it should, with the messages:
> > sponge:sf 500:arm/bin/arm-elf-gcc -mthumb-interwork -msoft-float
> > -mcpu=arm926ej-s -c demo.c
> > if I remove '-mcpu=arm926ej-s' from the compile, then the ld will
> > work, but i'll end up with floating point instructions on an arm
> > processor that has no fp.
> >
> pro@deb:~/armenv/bin$ ./arm-elf-gcc -c foo.c
> pro@deb:~/armenv/bin$ file foo.o
> foo.o: ELF 32-bit LSB relocatable, ARM, version 1 (ARM), not stripped
> pro@deb:~/armenv/bin$ ./arm-elf-ld -o demo.elf foo.o
> ../lib/gcc/arm-elf/4.1.0/libgcc.a
> Does this help you ? If not ask for more. You can add newlib or glibc
> after gcc bootstrap.
Thanks very much for taking the time to look at this. Sorry, but it
doesn't help. If you leave off the -mcpu=arm96ej-s option, than you
get an elf binary with floating point.
What I really need is instructions for building libgcc.a for arm w/o
any FP instructions in it, and especially, without the FP based
calling sequences. In particular, why did this work in 3.4 but not
4.1?
next prev parent reply other threads:[~2006-04-14 5:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 23:11 marty fouts
2006-04-13 7:25 ` Niklaus
2006-04-13 22:53 ` marty fouts
2006-04-14 4:53 ` Niklaus
2006-04-14 5:07 ` marty fouts [this message]
2006-04-14 6:18 ` Niklaus
2006-04-15 12:20 ` Hanumesh R
2006-04-16 6:48 ` Niklaus
2006-04-17 19:43 ` Free Lunch cino hilliard
2006-04-18 10:14 ` Andrew Haley
2006-04-18 20:52 ` cino hilliard
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=9f7850090604132207u4e4040cvc279877865737346@mail.gmail.com \
--to=mf.danger@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=niklaus@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).