Re: [PATCH] unitialized memory access vs BIT_INSERT_EXPR

2017-07-25 Thread Richard Biener
On Fri, Jul 21, 2017 at 8:24 PM, Andrew Pinski wrote: > Hi, > Due to the way bit-field access lower is done, we can get an > unitialized memory load and this causes the unitialized warning to > kick in. > The case we have is: > temp_1 = BIT_FIELD_REF > temp_2 = BIT_INSERT > BIT_FIELD_REF = temp_

[PATCH] unitialized memory access vs BIT_INSERT_EXPR

2017-07-21 Thread Andrew Pinski
Hi, Due to the way bit-field access lower is done, we can get an unitialized memory load and this causes the unitialized warning to kick in. The case we have is: temp_1 = BIT_FIELD_REF temp_2 = BIT_INSERT BIT_FIELD_REF = temp_2 What this patch does is similar to what was done for the case of BIT