are there any .c files in <your-favorite-os/library-layer> that must be compiled
with the local flavor of no-strict-aliasing?
my guess would be to look at the malloc implementation
is it simply a matter of waving union's over the code to keep cXX happy?
union
{
Specific_t* specific;
void* generic;
} u;
u.generic = some_buffer_pointer;
u.specific->im_ok_with_c99 ? yes : no;
On Wed, 29 Feb 2012 10:42:54 +0100 =?KOI8-R?B?z8zYx8Egy9LZ1sHOz9fTy8HR?= wrote:
> Michal, I called it a bug because it is a C99 violation (ISO C99
> edition, section 6.5, paragraph 7 specifies that it is illegal - with
> exceptions - for pointers of different types to reference the same
> memory location) and AFAIK the ast sources should be C99 clean to
> allow maximum portability, across all platforms involved. Being C99
> clean is a requirement for Solaris too.
_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers
