> As no '.type' was set for save_boot_params_ret in start.S, binutils > did not track whether it was emitted as A32 or T32. By properly > marking save_boot_params_ret as a potential function entry, we can > make sure that the compiler will insert the appropriate instructions > for branching to save_boot_params_ret both for call-sites emitted as > A32 and T32. > > Reported-by: Andy Yan <andy....@rock-chips.com> > Signed-off-by: Philipp Tomsich <philipp.toms...@theobroma-systems.com> > Tested-by: Andy Yan <andy....@rock-chips.com> > --- > > Changes in v5: None > Changes in v4: None > Changes in v3: > - tracked the root-cause why no interwork branch was emitted and fixed > it using a '.type'-directive in start.S to mark save_boot_params_ret > as a (possible) function-entry. > > Changes in v2: None > > arch/arm/cpu/armv7/start.S | 1 + > 1 file changed, 1 insertion(+) >
Applied to u-boot-rockchip/next, thanks! _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
