This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Make alias_sets_conflict_p less conservative
> you are right if for
>
> char c[4];
>
> c has a declared type of char. Which would make
>
> char c[4];
> int *p = c;
> *p = 0;
>
> undefined. But the above is commonly used enough to make any
> declared character array handled the same as allocated storage is.
So you feel that we need to support it?
But we're actually creating an object of char * here in that second
statement. Perhaps we can use that knowlege somehow.
But pessimizing "char" with no pointers in sight just to support this
seems very bad. There must be some approach that works.