Shouldn't a jump to gcc 7.2 or 8 with the Retopoline patches included, be the target given meltdown/spectre mitigations? This is going to affect newer Arm (mvebu potentially) and atom/x86 builds - although these use grub generally so not so much specific to uboot not compiling.
-Joel On 14 February 2018 at 04:04, <p.wa...@gmx.at> wrote: > Hey guys, > > as of U-Boot v2018.01, the bootloader requires at least a GCC 6 based > toolchain > for ARM targets [1]. Building will fail with GCCs prior to 6. (I.e. current > default 5.5.0) > > For the Kirkwood target, I've prepared a patch to bring it to v2018.01, but > that would result > in a failed build as stated above. (Of course, when manually selecting GCC6 > as compiler > everything is fine) > > How can this situation be resolved? > -) Stick to U-Boot 2017.11 until GCC 6.x is the default here? > -) Is a switch to GCC6 planned in the near future? > -) Undo the changes in [1] via a local patch and check, whether GCC5 is still > fine for Kirkwood? > > While the bootloader may not be that important in day to day business, > eventually a 'regular' > package might have a requirement for a newer compiler too... > > Best, > P. Wassi > > [1]: > http://git.denx.de/?p=u-boot.git;a=commit;h=6b867dabe84bae1e74e88f4af620c26cb793c4c2 > > > > _______________________________________________ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
