Skip to contentSkip to conversation

New: Optimize for fast -Ofast is not compliant

Buildroot bugzilla at busybox.net 1 participant 3 messages Jun 30, 2020 – Jul 18, 2020

lore
Share & tools
lore

bugzilla at busybox.net

author
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=13046

Bug ID: 13046
Summary: Optimize for fast -Ofast is not compliant
Product: buildroot
Version: 2020.05
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: sveyret at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

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!)?.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
author
#2 lore raw

[Buildroot] [Bug 13046] Optimize for fast -Ofast is not compliant

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=13046

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #1 from Thomas Petazzoni <[email protected]> --- Fixed by
https://git.buildroot.org/buildroot/commit/?id=3e186cee008f94f6a33adeac329b13087ab11ddb.
Thanks!

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.