All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation faults after gcc update
Date: Wed, 28 Sep 2011 11:18:16 +0200	[thread overview]
Message-ID: <1317201686.30002.1.camel@sven> (raw)
In-Reply-To: <20110927233638.303328c9@skate>

On Tue, 2011-09-27 at 23:36 +0200, Thomas Petazzoni wrote:
> Le Tue, 27 Sep 2011 10:04:12 +0200,
> Sven Neumann <s.neumann@raumfeld.com> a ?crit :
> 
> > What could possibly be wrong here? Is there anything else I need to
> > change when changing the version of gcc?
> 
> Other questions:
> 
>  * Is your CPU-specific compiler flags properly set ? Maybe they were
>    slightly wrong but working with gcc 4.3, and they no longer generate
>    appropriate code for your CPU with gcc 4.6. What is your CPU ? What
>    CPU-specific compiler flags are you using ?

This is a Marvell PXA300:

Processor	: XScale-V3 based processor rev 1 (v5l)
BogoMIPS	: 206.64
Features	: swp half thumb fastmult edsp iwmmxt 
CPU implementer	: 0x69
CPU architecture: 5TE
CPU variant	: 0x0
CPU part	: 0x688
CPU revision	: 1

And the relevant parts of the buildroot config are:

BR2_iwmmxt=y
BR2_ARM_TYPE="ARM_IWMMXT"
BR2_ARM_EABI=y
BR2_ARCH="arm"
BR2_ENDIAN="LITTLE"
BR2_GCC_TARGET_TUNE="iwmmxt"
BR2_GCC_TARGET_ARCH="iwmmxt"
BR2_GCC_TARGET_ABI="aapcs-linux"


Regards,
Sven

      reply	other threads:[~2011-09-28  9:18 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
2011-10-04  9:20         ` Sven Neumann
2011-09-27 21:36 ` Thomas Petazzoni
2011-09-28  9:18   ` Sven Neumann [this message]

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=1317201686.30002.1.camel@sven \
    --to=s.neumann@raumfeld.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 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.