Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13046] New: Optimize for fast -Ofast is not compliant
Date: Tue, 30 Jun 2020 08:16:21 +0000	[thread overview]
Message-ID: <bug-13046-163@https.bugs.busybox.net/> (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!)?.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-06-30  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  8:16 bugzilla at busybox.net [this message]
2020-06-30  8:18 ` [Buildroot] [Bug 13046] Optimize for fast -Ofast is not compliant bugzilla at busybox.net
2020-07-18 14:08 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13046-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox