This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/33102] volatile excessively suppresses optimizations in range checks
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Aug 2007 01:26:00 -0000
- Subject: [Bug middle-end/33102] volatile excessively suppresses optimizations in range checks
- References: <bug-33102-14989@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #13 from pinskia at gcc dot gnu dot org 2007-08-18 01:25 -------
(In reply to comment #11)
> The main concern on the recent LKML thread appeared to be code size rather than
> speed.
One should note this only helps CISC based processors, it will not help stuff
like PowerPC anyways. It is better to remove volatile in 95% of the places
where the kernel uses it anyways than fix this bug.
(In reply to comment #12)
> Please accept my apologies for skipping that step -- I wasn't aware of this.
> Should I replicate this bug at Ubuntu, or is this strictly advice for future
> bug submissions?
It would be better next time unless you can test it on a FSF GCC source
release/SVN.
Thanks,
Andrew Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33102