-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 10/02/2017 03:39 PM, Kyösti Mälkki wrote:
Hi Kyösti,
My fault, see: https://review.coreboot.org/21840
This fix booting issue. Thank you for quick reaction. Added +2 to review hope this not issue.
(...)
Once you have bisected to an offending commit, you can do builds that strips away all the revision hashes:
abuild --timeless -at pcengines/apu2 diff -qr build-ok/ build-fail/
The list of just the .o files is still a long one, but two further things you can do here: Strip debug symbols from .o files, and define ASSERT() without __FILE__ or __LINE__. If you know the commit was supposed to create a binary identical image, this is one way to pinpoint where the difference is.
This approach has saved the day before when AGESA includes have gone crazy.
Sounds like great approach. Any easy way to strip debug and redefine ASSERT in coreboot ? Or you just doing it manually ? Would be great to note exact steps in case anyone would need that in future. Maybe even script.
Best Regards, - -- Piotr Król Embedded Systems Consultant https://3mdeb.com | @3mdeb_com
-
Piotr Król