Overview
| Comment: | Also check for VFP2 if $host_cpu starts with earm
This is the case for NetBSD on some ARM boards. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
8c55f1870be9c536ffebd3a305ef63d9 |
| User & Date: | js on 2016-06-08 23:37:25 |
| Other Links: | manifest | tags |
Context
|
2016-06-09
| ||
| 00:25 | Use .init_array instead of .ctors on NetBSD/ARM check-in: 050216faa3 user: js tags: trunk | |
|
2016-06-08
| ||
| 23:37 | Also check for VFP2 if $host_cpu starts with earm check-in: 8c55f1870b user: js tags: trunk | |
| 23:22 | exception.m: More consistency in #ifdef order check-in: b919654740 user: js tags: trunk | |
Changes
Modified configure.ac from [0c3c6d689a] to [93ef7b6c04].
| ︙ | ︙ | |||
501 502 503 504 505 506 507 | ]) AC_MSG_RESULT($fp_endianess) AS_IF([test x"$fp_endianess" = x"unknown"], [ AC_MSG_ERROR( [Floating point implementation does not conform to IEEE 754!])]) case "$host_cpu" in | | | 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 |
])
AC_MSG_RESULT($fp_endianess)
AS_IF([test x"$fp_endianess" = x"unknown"], [
AC_MSG_ERROR(
[Floating point implementation does not conform to IEEE 754!])])
case "$host_cpu" in
arm* | earm*)
AC_MSG_CHECKING(if VFP2 or above is available)
AC_TRY_COMPILE([], [
__asm__ __volatile__ (
"fstmfdd sp!, {d0-d7}"
);
], [
AC_DEFINE(HAVE_VFP2, 1, [Whether we have VFP2 or above])
|
| ︙ | ︙ |