Re: [PATCH] Don't assume that constants can clobber vtbl

2011-10-19 Thread Maxim Kuvyrkov
On 11/10/2011, at 4:05 AM, Martin Jambor wrote: > > Just before this, there is the following test (guarded by > flag_strict_aliasing per explicit Richi's request). > > if (flag_strict_aliasing > && !POINTER_TYPE_P (TREE_TYPE (lhs))) > return false; > > Why is it n

Re: [PATCH] Don't assume that constants can clobber vtbl

2011-10-10 Thread Martin Jambor
On Mon, Oct 10, 2011 at 05:05:14PM +0200, Martin Jambor wrote: > Hi, > > sorry that taking care of the devirtualization patches takes me longer > than expected for various reasons. But I have not forgotten about > this. Ah, please ignore the attachment, I was trying to persuade mutt to add it to

Re: [PATCH] Don't assume that constants can clobber vtbl

2011-10-10 Thread Martin Jambor
Hi, sorry that taking care of the devirtualization patches takes me longer than expected for various reasons. But I have not forgotten about this. On Sat, Oct 01, 2011 at 01:58:57PM +1300, Maxim Kuvyrkov wrote: > This patch makes detect_type_change analysis assume that only ADDR_EXPRs can > be

[PATCH] Don't assume that constants can clobber vtbl

2011-09-30 Thread Maxim Kuvyrkov
This patch makes detect_type_change analysis assume that only ADDR_EXPRs can be assigned to vtable entries. Initially, the patch made a less strict assumption that constants are not assigned to vtables. I then bumped the assumption to "only ADDR_EXPRs can be assigned to vtables". I have this