From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] C double type problem - at91sam9263
Date: Wed, 06 Aug 2008 15:36:58 +0200 [thread overview]
Message-ID: <4899A8FA.5030903@cetrtapot.si> (raw)
In-Reply-To: <223E6519BDCAC74695BEE9D163F8E6592306FB@oakleaf10.oakleafconsultancy.com>
Richard Hardy wrote:
> I am using arm-linux-gcc v4.2.1., compiled on an intel Linux box to run
> on an atmel at91sam9263.
>
> For example, one problem I found was that I was getting stack
> corruptions when using "-Os" as a compiler option in (some) functions
> that were being passed int64_t and double values. I fixed that by using
> "-O0" instead.
>
That sounds like a compiler problem...
> However, I am getting lots of other really weird segmentation faults
> when I run the compiled program, which I am having to work around one by
> one (I am trying to cross-compile and use ffmpeg which does lots of
> complicated internal calculations for playing mpeg files).
>
> Is it possible that gcc 4.2.1 is a very buggy compiler version? Can
> anyone suggest whether I might be better to try another version (ideally
> one that Buildroot supports), and if so, which one?
I guess you would be better off using latest compiler available in 4.2.x series - 4.2.3 or 4.2.4 that is. I had a lot of issues with different gcc versions for cris architecture (internal compiler errors, segafaults, etc.) and ended up using 4.3.1 that does the job for now ;)
my 2 c..
--
?ETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar at cetrtapot.si
Http: www.cetrtapot.si
next prev parent reply other threads:[~2008-08-06 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 13:16 [Buildroot] C double type problem - at91sam9263 Richard Hardy
2008-08-06 13:36 ` Hinko Kocevar [this message]
2008-08-06 16:37 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2008-08-05 10:51 Richard Hardy
2008-08-05 16:37 ` Christopher Taylor
2008-08-04 13:58 Richard Hardy
2008-08-04 14:16 ` Hinko Kocevar
2008-08-04 21:27 ` Matthew Dombroski
2008-08-05 8:31 ` Hinko Kocevar
2008-08-05 9:15 ` Hinko Kocevar
2008-08-04 13:52 Richard Hardy
2008-08-04 10:29 Richard Hardy
2008-08-04 12:41 ` John Voltz
2008-08-04 12:43 ` Hinko Kocevar
2008-08-05 10:20 ` Ulf Samuelsson
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=4899A8FA.5030903@cetrtapot.si \
--to=hinko.kocevar@cetrtapot.si \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.