From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Question: __ARM_EABI__
Date: Wed, 13 Jan 2010 21:17:25 +0000 [thread overview]
Message-ID: <20100113211725.GH28292@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190902089C9B@mi8nycmail19.Mi8.com>
On Wed, Jan 13, 2010 at 04:10:41PM -0500, H Hartley Sweeten wrote:
> I'll take your word on that.
>
> But, based on the code I would not expect to see the message at all:
>
> #if !defined (__ARM_EABI__)
> #warning Your compiler does not have EABI support.
> #warning ARM unwind is known to compile only with EABI compilers.
> #warning Change compiler or disable ARM_UNWIND option.
> #elif (__GNUC__ == 4 && __GNUC_MINOR__ <= 2)
> #warning Your compiler is too buggy; it is known to not compile ARM unwind support.
> #warning Change compiler or disable ARM_UNWIND option.
> #endif
>
> I'm getting this during the compile:
>
> CHECK arch/arm/kernel/unwind.c
> arch/arm/kernel/unwind.c:30:2: warning: Your compiler does not have EABI support.
> arch/arm/kernel/unwind.c:31:2: warning: ARM unwind is known to compile only with EABI compilers.
> arch/arm/kernel/unwind.c:32:2: warning: Change compiler or disable ARM_UNWIND option.
If you get an oops with your compiler version and you have unwind
support enabled, you _will_ _not_ get a backtrace. That's because
EABI support in gcc 4.3.2 is incomplete.
As the message says, either use a later compiler or disable unwind
support.
next prev parent reply other threads:[~2010-01-13 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 19:08 Question: __ARM_EABI__ H Hartley Sweeten
2010-01-13 20:27 ` Mikael Pettersson
2010-01-13 20:57 ` H Hartley Sweeten
2010-01-13 21:05 ` Russell King - ARM Linux
2010-01-13 21:10 ` H Hartley Sweeten
2010-01-13 21:17 ` Russell King - ARM Linux [this message]
2010-01-13 21:32 ` H Hartley Sweeten
2010-01-13 23:30 ` Mikael Pettersson
2010-01-14 0:11 ` H Hartley Sweeten
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=20100113211725.GH28292@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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