From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation faults after gcc update
Date: Mon, 20 Feb 2012 08:55:35 -0800 [thread overview]
Message-ID: <20120220085535.2246a727@skate> (raw)
In-Reply-To: <1329734220.13226.35.camel@bender>
Le Mon, 20 Feb 2012 11:37:00 +0100,
Sven Neumann <s.neumann@raumfeld.com> a ?crit :
> It turned out that Thomas guessed right. It seems that the iwmmxt
> optimizations are broken in gcc newer than 4.3. Changing the target to
> xscale fixed the problem. And the tests I have done so far seem to
> imply that the performance of code compiled with gcc 4.6 optimized
> for xscale is slightly better than the same code compiled with gcc
> 4.3 optimized for iwmmxt.
Ok.
> Not sure if this should somehow be handled in buildroot. But I thought
> I'd at least let you know on the mailing-list so that others can avoid
> running into the same problem.
If the problem is still there in the latest versions of gcc, it should
be reported as a bug to the gcc project.
Thanks for the investigation!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-02-20 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 8:04 [Buildroot] Segmentation faults after gcc update Sven Neumann
2011-09-27 21:35 ` Thomas Petazzoni
2011-09-28 8:57 ` Sven Neumann
2011-09-28 14:44 ` Sven Neumann
2011-09-30 9:06 ` Sven Neumann
2011-09-30 19:59 ` Thomas Petazzoni
2011-09-30 20:35 ` Thomas Petazzoni
2012-02-20 10:37 ` Sven Neumann
2012-02-20 16:55 ` Thomas Petazzoni [this message]
2011-10-04 9:20 ` Sven Neumann
2011-09-27 21:36 ` Thomas Petazzoni
2011-09-28 9:18 ` Sven Neumann
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=20120220085535.2246a727@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox