Author: Armin Rigo <ar...@tunes.org>
Branch:
Changeset: r80339:b5e12e911be2
Date: 2015-10-19 20:10 +0200
http://bitbucket.org/pypy/pypy/changeset/b5e12e911be2/
Log: :-(
diff --git a/rpython/translator/c/src/stacklet/switch_arm_gcc.h
b/rpython/translator/c/src/stacklet/switch_arm_gcc.h
--- a/rpython/translator/c/src/stacklet/switch_arm_gcc.h
+++ b/rpython/translator/c/src/stacklet/switch_arm_gcc.h
@@ -62,6 +62,15 @@
, "d0", "d1", "d2", "d3", "d4", "d5", "d6", "d7"
, "d8", "d9", "d10", "d11", "d12", "d13", "d14", "d15"
/* messsssssssssssss quite unsure it is the correct way */
+/* Actually it seems there is no way. These macros are defined by ARM's
+ * own compiler but not by GCC. On GCC, by looking at its sources it
+ * seems that we'd like to know the internal TARGET_VFPD32 flag, but
+ * there is no way to access it because it's not exported as a macro.
+ * We loose. If you compile for some architecture with 32 "d"
+ * registers, gcc will likely move the registers to save (d8-d15)
+ * into some of d16-d31, and they will then be clobbered.
+ * I don't see any solution. :-((
+ */
# if defined(__TARGET_FPU_SOFTVFP_VFPV3) || \
defined(__TARGET_FPU_SOFTVFP_VFPV3_FP16) || \
defined(__TARGET_FPU_VFPV3) || \
_______________________________________________
pypy-commit mailing list
pypy-commit@python.org
https://mail.python.org/mailman/listinfo/pypy-commit
