Marc Jones 5f145faff8 Don't do a call as the first instruction in libpayload. ... Doing a call before the payload has set up its stack is risky. The stack may not be in a favorable location. Normally this is not an issue with coreboot or other well behaved callers. Change-Id: Ie6f6748a471324b29ebad045c807dfc9f4b92034 Signed-off-by: Marc Jones <marcj303@gmail.com> Reviewed-on: http://review.coreboot.org/240 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>		2011-10-11 11:47:06 +02:00
..
Makefile.inc	Use coreboot build system for libpayload, too.	2011-06-30 20:40:10 +02:00
coreboot.c	Reduce warnings/errors in libpayload when using picky compiler options	2011-06-30 20:41:23 +02:00
exec.S	…
head.S	Don't do a call as the first instruction in libpayload.	2011-10-11 11:47:06 +02:00
main.c	Reduce warnings/errors in libpayload when using picky compiler options	2011-06-30 20:41:23 +02:00
multiboot.c	Reduce warnings/errors in libpayload when using picky compiler options	2011-06-30 20:41:23 +02:00
sysinfo.c	…
timer.c	prevent timer overflows in libpayload	2010-03-25 18:53:20 +00:00
util.S	…
virtual.c	Reduce warnings/errors in libpayload when using picky compiler options	2011-06-30 20:41:23 +02:00