Avoid build errors with -O0 due to assembly

This commit is contained in:
Manuel Pégourié-Gonnard 2016-01-08 14:29:11 +01:00
parent bb81b4a009
commit 7715e669f1
2 changed files with 22 additions and 1 deletions

View file

@ -8,6 +8,11 @@ Bugfix
Follath. #309
* Fix issue in Makefile that prevented building using armar. #386
Changes
* On ARM platforms, when compiling with -O0 with GCC, Clang or armcc5,
don't use the optimized assembly for bignum multiplication. This removes
the need to pass -fomit-frame-pointer to avoid a build error with -O0.
= mbed TLS 2.1.4 released 2016-01-05
Security

View file

@ -563,7 +563,23 @@
#endif /* TriCore */
#if defined(__arm__)
/*
* gcc -O0 by default uses r7 for the frame pointer, so it complains about our
* use of r7 below, unless -fomit-frame-pointer is passed. Unfortunately,
* passing that option is not easy when building with yotta.
*
* On the other hand, -fomit-frame-pointer is implied by any -Ox options with
* x !=0, which we can detect using __OPTIMIZE__ (which is also defined by
* clang and armcc5 under the same conditions).
*
* So, only use the optimized assembly below for optimized build, which avoids
* the build error and is pretty reasonable anyway.
*/
#if defined(__GNUC__) && !defined(__OPTIMIZE__)
#define CANNOT_USE_R7
#endif
#if defined(__arm__) && !defined(CANNOT_USE_R7)
#if defined(__thumb__) && !defined(__thumb2__)