From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules
Date: Tue, 31 Aug 2010 17:30:39 -0500 [thread overview]
Message-ID: <4C7D828F.6040905@freescale.com> (raw)
I ran Software Update on my Fedora 13 system, and now whenever I build
U-Boot, I get a bunch of warnings like this:
dlmalloc.c: In function 'malloc':
dlmalloc.c:2252: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2252: note: initialized from here
dlmalloc.c:2261: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2261: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2261: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2261: note: initialized from here
dlmalloc.c:2268: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2268: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2268: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2268: note: initialized from here
dlmalloc.c:2325: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2325: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2325: warning: dereferencing pointer '({anonymous})' does break
strict-aliasing rules
dlmalloc.c:2325: note: initialized from here
Can anyone explain why this is happening? I don't understand how a Fedora
update would change anything, since my cross-compile toolchain is not
distributed with Fedora, so it shouldn't have changed.
next reply other threads:[~2010-08-31 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 22:30 Timur Tabi [this message]
2010-09-01 17:01 ` [U-Boot] warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules Mike Frysinger
2010-09-02 1:27 ` Timur Tabi
2010-09-02 5:07 ` Mike Frysinger
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=4C7D828F.6040905@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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.