This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Would alias analysis help WRT builtin memmove -> builtin memcpy ?
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: Would alias analysis help WRT builtin memmove -> builtin memcpy ?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 29 Mar 2000 16:36:21 -0700
- cc: egcs at egcs dot cygnus dot com
- Reply-To: law at cygnus dot com
In message <200003292334.SAA02200@caip.rutgers.edu>you write:
> Right, but then shouldn't it have returned set 0, not 11?
Depends on the code :-) I believe if you had casted the arg to a void *
then you would have got an alias set zero. Actually, wait, you have two
pointers, not two MEMs -- how are you checking alias sets in that case
since the alias set is a property of the MEM, not the address.
So, no, I don't see a way to do easily what you want since our aliasing
code is designed to work on MEMs, not addresses.
You might be able to generate a MEM with the unknown alias set (-1 I think)
and pass that to the aliasing routines. Not really sure.
jeff