From: ng@piments.com
To: Martin Guy <martinwguy@gmail.com>,
Crossgcc list <crossgcc@sourceware.org>
Subject: Re: -mfloat-abi=softfp
Date: Tue, 27 Apr 2010 18:55:00 -0000 [thread overview]
Message-ID: <4BD73332.8060507@piments.com> (raw)
In-Reply-To: <v2j56d259a01004270621i6e44dbb2p87cc64e96b5c6032@mail.gmail.com>
On 04/27/10 15:21, Martin Guy wrote:
> On 4/27/10, ng@piments.com<ng@piments.com> wrote:
>> Uptil now I was using -march=armv4t , setting it ep9312 fails on 4.2.4
>>
>>
>> [ALL ]
>> /back/ts/ct-ng/targets/src/gcc-4.2.4/gcc/crtstuff.c:1:
>> warning: target CPU does not support interworking
>> [ALL ] Assembler messages:
>> [ALL ] Error: unknown architecture `ep9312'
>> [ALL ]
>> [ALL ] Error: unrecognized option -march=ep9312
>
> THat's not GCC. That's the assembler (binutils).
Thanks , I've just got your email about comsic rays ;)
I'd already realised that part of the reason for the seg fauilts looks
like it was hardware instability. I ran some stress tests (other than
ct-ng :P ) and it tripped out as well.
I've lowered the system clock and that seems to have stabilised it for
now , until I have time to strip it down.
However, I did still have _repeatable_ seg faults as I reported in an
earlier post.
> Yeah, this whole area is a pain. Can you drop the empty -march switch
> and use -mcpu-ep9312? That's the only combinatin that seems to work
> with GCC and the assembler
That's it !
I dropped all use of -march and only use ep9312 rather than armv4t
LIBC_GLIBC_EXTRA_CFLAGS=-mfpu=maverick -mfloat-abi=softfp -mcpu=ep9312
CT_ARCH_CPU = ep9312
I had to move to starce-4.5.19 as well because of headers. I now have
managed to configure ct-ng to build a nice new crunchy toolchain.
It remains to see if it can produce useful code....
thanks again for your help and guidance.
best regards.
>
>> Could this relate to the -march= switch message I was getting before. Is
>> some other stage deciding this is invalid and replacing it with a null
>> string?
>
> If ther is an empty -march or -march=armv4t it's probably best not to
> have *any* -march flag. You may have to hack crosstool-ng to achieve
> this, I don't know.
>
> M
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2010-04-27 18:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 18:39 -mfloat-abi=softfp ng
2010-04-18 18:58 ` -mfloat-abi=softfp Martin Guy
2010-04-19 1:22 ` -mfloat-abi=softfp ng
2010-04-19 9:52 ` -mfloat-abi=softfp Martin Guy
2010-04-19 9:53 ` -mfloat-abi=softfp Martin Guy
2010-04-19 17:53 ` -mfloat-abi=softfp ng
2010-04-19 18:16 ` -mfloat-abi=softfp Martin Guy
2010-04-19 18:21 ` -mfloat-abi=softfp Martin Guy
2010-04-27 10:13 ` -mfloat-abi=softfp ng
2010-04-27 11:08 ` -mfloat-abi=softfp Martin Guy
2010-04-27 12:58 ` -mfloat-abi=softfp ng
[not found] ` <v2j56d259a01004270621i6e44dbb2p87cc64e96b5c6032@mail.gmail.com>
2010-04-27 18:55 ` ng [this message]
2010-04-27 13:27 ` -mfloat-abi=softfp ng
2010-04-27 15:25 ` -mfloat-abi=softfp Martin Guy
[not found] ` <4BD7CBFD.8010702@piments.com>
[not found] ` <q2v56d259a01004280152t2d59959ah57cdf11440f63c06@mail.gmail.com>
2010-04-29 20:20 ` -mfloat-abi=softfp ng
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=4BD73332.8060507@piments.com \
--to=ng@piments.com \
--cc=crossgcc@sourceware.org \
--cc=martinwguy@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).