[U-Boot] [PATCH 1/4] Reactivate the tracing feature

[Masahiro Yamada]

Hi Simon,


On Wed, 11 Jun 2014 23:50:48 -0400
Simon Glass <sjg at chromium.org> wrote:

> Hi Masahiro,
> 
> On 11 June 2014 23:42, Simon Glass <sjg at chromium.org> wrote:
> > Hi Masahiro,
> >
> > Yes I should remove this otherwise it will at best bloat the code for
> > SPL. I think it is probably best just to revert that part of the
> > Makefile.
> 
> Although actually I'm not sure how to have different flags for
> everything except SPL and examples/ - any clues?

Me neither.

But one possible solution is:

Add  the CONFIG_SPL_BUILD conditional to config.mk
to disable it for SPL.

ifeq ($(CONFIG_SPL_BUILD),)
ifdef FTRACE
CFLAGS += -finstrument-functions -DFTRACE
endif
endif



exmpales/  seems having troubles with FTRACE.
So, disable it when FTRACE=1 is defined.

examples/Makefile is like this:

ifndef FTRACE
ifndef CONFIG_SANDBOX
subdir-y += standalone
subdir-$(CONFIG_API) += api
endif
endif



BTW,  can  FTRACE build for all boards?

I checked out v2014.01 (pre-kbuild)

- make sandbox_config;  make FTRACE=1
- make snow_config;  make CROSS_COMPILE=arm-linux-gnueabi- FRACE=1

succeeded. But, 

- make omap3_beagle_config; make CROSS_COMPILE=arm-linux-gnueabi- FRACE=1

faied with lots of  undefined reference errors to __cyg_profile_func_enter/_exit.


I don't know why.



Best Regards
Masahiro Yamada