------- Comment #2 from contact at philipashmore dot com 2010-08-06 13:37
-------
It's exactly what I tried first - I know there are obvious cases as per your
"frequently reported bugs" section.
I wanted the compiler to tell me where the aliasing was occurring in these and
in
any less obvious places so I could disable aliasing optimizations in these
cases.
Currently it's missing even the ones the docs claims it should spot - pointer->
uintptr_t -> pointer.
Previous release of treedb didn't need -fno-strict-aliasing, or did they?
If the compiler can't spot aliasing should -fno-strict-aliasing be the default?
--
contact at philipashmore dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |contact at philipashmore dot
| |com
Status|WAITING |UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45204
