[Buildroot] [PATCH] utils/genrandconfig: filter microblaze GCC < 8 bug
thomas.petazzoni at bootlin.com
Thu May 24 11:30:29 UTC 2018
On Wed, 23 May 2018 16:53:46 -0500, Matt Weber wrote:
> Works around https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85180
> which is an issue where the Microblaze archtecture had code that
> caused a infinite recursion while optimizing in versions of GCC
> less then 8.x. More BR discussion can be found on this thread.
> CC: Romain Naour <romain.naour at gmail.com>
> Signed-off-by: Matthew Weber <matthew.weber at rockwellcollins.com>
I don't see why we would do autobuilder exceptions for this rather than
a usual BR2_TOOLCHAIN_GCC_HAS_BUG_xyz.
If I understand correctly, we have two issues:
- gcc bug #85862, which didn't exist in gcc 6.3 and is a regression in
gcc 6.4, but doesn't exist in gcc 7.x
This bug affects the build of libnss, and was handled by commit
bd03966d4ebeb284ac3afb5f3b8cba13da2b9983, through the addition of
- gcc bug #85180, which affects gcc 6.x and gcc 7.x, but is fixed in
gcc 8.x. It affects packages such as flare-engine, boost and
So, for this one, rather than autobuilder exception, I would like to
see something like this:
default y if BR2_microblaze
and we'll adjust this with a "depends on BR2_TOOLCHAIN_GCC_AT_LEAST_8"
when gcc 8.x support is added in Buildroot.
flare-engine is not selected by any package (flare-game depends on
gst-ffmpeg is not selected by any package.
boost has lots of reverse dependencies however. But perhaps we can nail
down the specific boost sub-option(s) that exhibit the problem, and
only add the gcc bug dependency on those suboptions?
Any reason for not using this solution ?
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
More information about the buildroot