[Buildroot] [autobuild.buildroot.net] Build results for 2018-04-25

[Romain Naour <romain.naour@gmail.com>]

Hi All,

Le 26/04/2018 ? 08:00, Thomas Petazzoni a ?crit?:
> Hello,
> 
> Build statistics for 2018-04-25
> ===============================
> 
>       branch |  OK | NOK | TIM | TOT |
>    2018.02.x |  31 |   3 |   0 |  34 |
>       master | 170 |  54 |   3 | 227 |
> 
> Results for branch 'master'
> ===========================
> 
> Classification of failures by reason
> ------------------------------------
>
>                          boost | 1 
>                   flare-engine | 1 
> 
> Detail of failures
> ------------------
> 
> microblazeel |                          boost | TIM | http://autobuild.buildroot.net/results/b42d68c66d8ea035845a28c5530ef0682fd95713 |     
> microblazeel |                   flare-engine | TIM | http://autobuild.buildroot.net/results/af976a4805fb8b3f0c17a8e3a1f901b2255caa0b |     

I tried to reproduce this issue with the upcoming gcc 8.1 for microblaze but
flare-engire build fine with it.

git bisect helped to find a patch [1] fixing an infinite loop in RTL DSE
optimizer. Also, back porting the patch to gcc 7.3.0 fix the issue.

Since this patch is not specific to microblaze, but in gcc's code, I'm not sure
what we need to do.
Either back port the patch to affected gcc version and take the risk to break
something with other architecture or optimization level.
Or add BR2_TOOLCHAIN_HAS_GCC_BUG_85180 option and wait for gcc 8.

Maybe it's easier to add an autobuilder exception for boost and flare-engine on
microblaze?

It's not clear if other architecture can be affected.

Thoughts?

Best regards,
Romain

[1]
https://github.com/gcc-mirror/gcc/commit/df03ebc3574a0d7893127e3b9754a01abf2d8b70
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85180