From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules
Date: Wed, 1 Sep 2010 13:01:53 -0400 [thread overview]
Message-ID: <201009011301.54737.vapier@gentoo.org> (raw)
In-Reply-To: <4C7D828F.6040905@freescale.com>
On Tuesday, August 31, 2010 18:30:39 Timur Tabi wrote:
> I ran Software Update on my Fedora 13 system, and now whenever I build
> U-Boot, I get a bunch of warnings like this:
what version of u-boot exactly ? for what board/architecture ? what is your
host gcc version and your target gcc version ? what is the exact compile line
that causes this warning to be displayed ? this is a pretty information-less
bug report ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100901/869f3309/attachment.pgp
next prev parent reply other threads:[~2010-09-01 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 22:30 [U-Boot] warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules Timur Tabi
2010-09-01 17:01 ` Mike Frysinger [this message]
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=201009011301.54737.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox