diff options
Diffstat (limited to 'meta-oe/recipes-devtools/nodejs/nodejs/fix-hardfloat-detection.patch')
| -rw-r--r-- | meta-oe/recipes-devtools/nodejs/nodejs/fix-hardfloat-detection.patch | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs/fix-hardfloat-detection.patch b/meta-oe/recipes-devtools/nodejs/nodejs/fix-hardfloat-detection.patch new file mode 100644 index 0000000000..36e8bf1c97 --- /dev/null +++ b/meta-oe/recipes-devtools/nodejs/nodejs/fix-hardfloat-detection.patch @@ -0,0 +1,22 @@ +Fix hardfloat detection + +gcc has a builtin define to denote hard abi when in use, e.g. when +using -mfloat-abi=hard it will define __ARM_PCS_VFP to 1 and therefore +we should check that to determine which calling convention is in use +and not __VFP_FP__ which merely indicates presence of VFP unit + +The fix has been provided by Khem Raj <raj.khem@gmail.com> + +Upstream-Status: Forwarded + +--- a/deps/v8/src/platform-linux.cc 2012-05-17 12:52:59.329519921 -0700 ++++ b/deps/v8/src/platform-linux.cc 2012-05-17 12:54:02.037521511 -0700 +@@ -212,7 +212,7 @@ + // calling this will return 1.0 and otherwise 0.0. + static void ArmUsingHardFloatHelper() { + asm("mov r0, #0"); +-#if defined(__VFP_FP__) && !defined(__SOFTFP__) ++#if defined(__ARM_PCS_VFP) && !defined(__SOFTFP__) + // Load 0x3ff00000 into r1 using instructions available in both ARM + // and Thumb mode. + asm("mov r1, #3"); |