From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1339] New: Busybox needs -fno-stric-aliasing to compile cleanly
Date: Wed, 17 Mar 2010 15:38:43 +0000 (UTC) [thread overview]
Message-ID: <bug-1339-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1339
Host: Gentoo Linux
Target: Atmel ARM9
Build: 2010.2
Summary: Busybox needs -fno-stric-aliasing to compile cleanly
Product: buildroot
Version: 2010.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: grant.b.edwards at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=1315)
--> (https://bugs.busybox.net/attachment.cgi?id=1315)
Fix strick-aliasing compiler warnings
When busybox is compiled (with gcc 4.4.3), there are thousands of
compiler warnings about code that is breaking the strict aliasing
rules that must be followed if -O2 or greater optimization level is to
be used.
Adding -fno-strict-aliasing to CFLAGS fixes this problem.
Patch is attached.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-03-17 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 15:38 bugzilla at busybox.net [this message]
2010-03-17 15:39 ` [Buildroot] [Bug 1339] Busybox needs -fno-strict-aliasing to compile cleanly bugzilla at busybox.net
2010-03-17 15:39 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-07-18 19:15 ` bugzilla at busybox.net
2010-07-18 20:14 ` bugzilla at busybox.net
2010-07-22 15:12 ` 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-1339-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.