[re-adding the mailinglist]
On Wed, Oct 29, 2014 at 9:41 AM, Richard Purdie
wrote:
> On Wed, 2014-10-29 at 07:47 +0100, Kristof Robot wrote:
>> On Tue, Oct 28, 2014 at 11:08 PM, Richard Purdie
>> wrote:
>> > On Tue, 2014-10-28 at 19:11 +0100, Kristof Robot wrote:
>>
On Mon, Oct 27, 2014 at 11:59 PM, Richard Purdie
wrote:
> On Mon, 2014-10-27 at 20:54 +0100, Kristof Robot wrote:
>> Richard, all,
>>
>> After bisecting, I found that, since this patch, my toolchain is being
>> built with soft floating point support, while it should be
Richard, all,
After bisecting, I found that, since this patch, my toolchain is being
built with soft floating point support, while it should be built with
hard floating point support:
(1) Compiling parent commit 74d8866814aec520822518cc4cb8a942f7069bf7
[1] gives hard floating point support (good)
On Sat, Jan 11, 2014 at 4:08 PM, Andrei Gherzan wrote:
> Avoid a confusion when including thumb in TUNE_FATURES. In the curent
> behavior,
> if I include thumb in TUNE_FATURES, ARM_THUMB_M_OPT will be "-marm" which
> makes
> no sense for me as a default behavior.
I agree that this is confusing,
[YOCTO #5710]
Add tuning options for Cortex-A7 with NEONv2 & FPv4:
- cortexa7hf-neon-vfpv4
- cortexa7thf-neon-vfpv4
Signed-off-by: Kristof Robot
---
meta/conf/machine/include/arm/arch-armv7a.inc | 8 +++-
meta/conf/machine/include/arm/feature-arm-neon.inc | 4 ++--
meta/conf/mac
