This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
more strict-aliasing questions
- From: howarth at bromo dot msbb dot uc dot edu (Jack Howarth)
- To: gcc at gcc dot gnu dot org
- Date: Mon, 5 Dec 2005 13:01:05 -0500 (EST)
- Subject: more strict-aliasing questions
Is there some place where all the existing forms of strict-aliasing
warnings are documented? So far I have only seen the error...
dereferencing type-punned pointer will break strict-aliasing rules
when building c++ code with gcc trunk (4.2). I am wondering how many other
types of warnings can -Wstrict-aliasing issue besides this one for gcc and
of those how many of those are currently checked in the g++ compiler?
My second question is how univeral are the strict-aliasing rules used
by gcc? In other words, is it safe to say that by correcting source code
upstream to not violate any of the strict-aliasing rules in gcc trunk that
such code might achieve stability benefits as well on other third party
compilers? Or are these strict-aliasing rules pretty much gcc-specific?
Thanks in advance for any clarifications.
Jack