Unroll loops for all firmware platforms
Unrolling loops shaves 20ms off pit ro boot time. This option was
enabled before but inadvertently got disabled for ARM.
BUG=chrome-os-partner:2115
BRANCH=pit
TEST=manual
Build for pit, see that code size increases slignly but RO boot time
drops by about 24ms.
Original size:
text data bss dec hex filename
422482 17580 334796 774858 bd2ca b/chromeos_peach/u-boot
14938 1111 0 16049 3eb1 b/chromeos_peach/spl/u-boot-spl
New size:
429322 17580 334788 781690 bed7a b/chromeos_peach/u-boot
14938 1111 0 16049 3eb1 b/chromeos_peach/spl/u-boot-spl
Change-Id: I1ded0ed3369de9d72220112b92c322777d1ba2d5
Signed-off-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/168803
Reviewed-by: Randall Spangler <rspangler@chromium.org>
diff --git a/Makefile b/Makefile
index 403b4d6..7d0956a 100644
--- a/Makefile
+++ b/Makefile
@@ -626,10 +626,12 @@
# CFLAGS += -DTPM_MANUAL_SELFTEST
-ifeq (${FIRMWARE_ARCH},i386)
+ifneq (${FIRMWARE_ARCH},)
# Unrolling loops in cryptolib makes it faster
${FWLIB_OBJS}: CFLAGS += -DUNROLL_LOOPS
+endif
+ifeq (${FIRMWARE_ARCH},i386)
# Workaround for coreboot on x86, which will power off asynchronously
# without giving us a chance to react. This is not an example of the Right
# Way to do things. See chrome-os-partner:7689, and the commit message
