Aliasing violation generated by fold_builtin_memcmp?

Andrew Pinski pinskia@physics.uc.edu
Fri Sep 30 17:50:00 GMT 2005


On Sep 29, 2005, at 8:32 PM, Daniel Berlin wrote:

>
>> Any suggestions how to fix this?
>
> The easiest thing is to store a version of unsigned_char_type_node
> somewhere that has it's TYPE_ALIAS_SET set to 0, and use it there.
> Whether this is the best solution, i'll leave to others :)


Something like this will fix the issue with TYPE_REF_CAN_ALIAS_ALL
by removing the use.  Maybe we could move may_alias to a bit in the
types and move TYPE_REF_CAN_ALIAS_ALL from the pointer type to the
type which is being accessed instead of this mess.

-- Pinski


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: t6543.diff.txt
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20050930/42e1ba3a/attachment.txt>


More information about the Gcc mailing list