From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored
Date: Sat, 22 Jan 2011 13:46:19 +0100 [thread overview]
Message-ID: <4D3AD19B.6030102@ahsoftware.de> (raw)
Hello,
because I've recently seen some other places where volatile is used to
access registers without using read?() or write?() and many people seem
to start using 4.5.1, I want to post this warning using a descriptive
subject.
The keyword volatile might not have any effect when reading when gcc
4.5.0 or 4.5.1 is used.
The appropriate bug seems to be that one:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45052
You might either change such code to use readb(), readw() or readl(), or
you have to use either an older version of gcc or a version >= 4.5.2 (it
is fixed in 4.5.2).
A patch for write?() and read?() is currently in the
u-boot-arm-repository (but not in the master and not in 2010.12):
http://lists.denx.de/pipermail/u-boot/2011-January/084885.html
Regards,
Alexander
next reply other threads:[~2011-01-22 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 12:46 Alexander Holler [this message]
2011-01-22 14:14 ` [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored Wolfgang Denk
2011-01-22 17:40 ` Dirk Behme
2011-01-22 18:03 ` Albert ARIBAUD
2011-01-22 19:30 ` Wolfgang Denk
2011-01-22 20:23 ` Albert ARIBAUD
2011-01-24 13:03 ` Wolfgang Denk
2011-01-24 18:18 ` Albert ARIBAUD
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=4D3AD19B.6030102@ahsoftware.de \
--to=holler@ahsoftware.de \
--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