[prev in list] [next in list] [prev in thread] [next in thread] 

List:       buildroot
Subject:    [Buildroot] [Bug 13046] New: Optimize for fast -Ofast is not compliant
From:       bugzilla () busybox ! net
Date:       2020-06-30 8:16:21
Message-ID: bug-13046-163 () https ! bugs ! busybox ! net/
[Download RAW message or body]

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@buildroot.uclibc.org
          Reporter: sveyret@gmail.com
                CC: buildroot@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!)".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

[prev in list] [next in list] [prev in thread] [next in thread]