Bug 13046

Summary: Optimize for fast -Ofast is not compliant
Product: buildroot Reporter: Stéphane Veyret <sveyret>
Component: OtherAssignee: unassigned
Status: RESOLVED FIXED    
Severity: normal CC: buildroot
Priority: P5    
Version: 2020.05   
Target Milestone: ---   
Hardware: All   
OS: Linux   
See Also: https://bugs.busybox.net/show_bug.cgi?id=13031
Host: Target:
Build:

Description Stéphane Veyret 2020-06-30 08:16:21 UTC 
In buildroot, it is possible to select the gcc optimization flag (Build options/gcc optimization level).

The flag -Ofast in gcc creates code that is not compliant to standards. This is written in gcc documentations, and also in the help when you select “optimize for fast” in “gcc optimization level”. But for someone creating an embedded system where speed is critical, he may select this optimization without reading the help, which would build non-working packages (I spent about a whole week searching why NodeJS was not working on my system!)

I suggest to indicate the problem in the label like, for example: “optimize for fast (may break packages!)”.