[Mesa-dev] [PATCH] Fix strict-aliasing violations in GLSL shader list implementation

[Matt Turner]

On Tue, Jun 23, 2015 at 6:44 PM, Ian Romanick <idr at freedesktop.org> wrote:
> Please quote the spec.

Section 6.5 Expressions of the draft C99 spec I have says (page 68, 80
of the pdf):

7 An object shall have its stored value accessed only by an lvalue
expression that has one of the following types: 76)

— a type compatible with the effective type of the object,

— a qualified version of a type compatible with the effective type of
the object,

— a type that is the signed or unsigned type corresponding to the
effective type of the object,

— a type that is the signed or unsigned type corresponding to a
qualified version of the effective type of the object,

— an aggregate or union type that includes one of the aforementioned
types among its members (including, recursively, a member of a
subaggregate or contained union), or

— a character type.

And the footnote 76 is:

76) The intent of this list is to specify those circumstances in which
an object may or may not be aliased.