Jack Howarth wrote:
Is there some place where all the existing forms of strict-aliasing
warnings are documented? So far I have only seen the error...
We don't have such documentation unfortunately. There are 3 errors.
There is the one you have seem. There is a similar one for incomplete
Jack Howarth writes:
> My second question is how univeral are the strict-aliasing
> rules used by gcc?
They are applicable to every compiler that implements ISO C++. In
other words, code that violates aliasing constrains is not legal C++.
> In other words, is it safe to say that by corr
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 ca
