This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/15850] extra load with volatilable variables
- From: "bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Jun 2004 19:56:25 -0000
- Subject: [Bug c/15850] extra load with volatilable variables
- References: <20040606151231.15850.pinskia@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bangerth at dealii dot org 2004-06-15 19:56 -------
Why is it wrong? It may be overly conservative, but I'd say that since
v1 = v2
returns the value of v1, the compiler has every right to reload v1 if
v1 happens to be volatile. Think v1 being a hardware register that returns
status values when read from that do not necessarily have anything to do
with what you write into them.
W.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15850