Re: [PATCH] Copy over TREE_THIS_VOLATILE during forwprop (PR tree-optimization/50078)

2011-11-28 Thread Jakub Jelinek
On Mon, Nov 28, 2011 at 12:16:45PM -0700, Jeff Law wrote: > > On the following testcase the volatile load/store are optimized > > away. IMHO this is a bug in forwprop, which replaces tmp_Y = > > &nonvolvar[arg_X]; MEM[(volatile ...*)tmp_Y] ={v} ...; with > > MEM[(volatile ...*)&nonvolvar][tmp_Y] =

Re: [PATCH] Copy over TREE_THIS_VOLATILE during forwprop (PR tree-optimization/50078)

2011-11-28 Thread Jeff Law
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/28/11 11:36, Jakub Jelinek wrote: > Hi! > > On the following testcase the volatile load/store are optimized > away. IMHO this is a bug in forwprop, which replaces tmp_Y = > &nonvolvar[arg_X]; MEM[(volatile ...*)tmp_Y] ={v} ...; with > MEM[(vola

[PATCH] Copy over TREE_THIS_VOLATILE during forwprop (PR tree-optimization/50078)

2011-11-28 Thread Jakub Jelinek
Hi! On the following testcase the volatile load/store are optimized away. IMHO this is a bug in forwprop, which replaces tmp_Y = &nonvolvar[arg_X]; MEM[(volatile ...*)tmp_Y] ={v} ...; with MEM[(volatile ...*)&nonvolvar][tmp_Y] ={v} ...; where the LHS is no longer TREE_THIS_VOLATILE like befo