Re: [PR tree-optimization/67955] Exploit PTA in DSE

2017-01-09 Thread Richard Biener
On January 9, 2017 6:02:16 PM GMT+01:00, Jeff Law wrote: >On 01/09/2017 02:36 AM, Richard Biener wrote: >>> >>> >>> a = 1; >>> >>> a = 2; >>> >>> >>> If "a" escapes such that its value can be queried in the exception >handler, >>> then the exception handler would be able to observe the first stor

Re: [PR tree-optimization/67955] Exploit PTA in DSE

2017-01-09 Thread Jeff Law
On 01/09/2017 02:36 AM, Richard Biener wrote: a = 1; a = 2; If "a" escapes such that its value can be queried in the exception handler, then the exception handler would be able to observe the first store and thus it should not be removed. Yes, and it won't as long as the EH is thrown inter

Re: [PR tree-optimization/67955] Exploit PTA in DSE

2017-01-09 Thread Richard Biener
On Sat, Jan 7, 2017 at 7:01 PM, Jeff Law wrote: > On 01/05/2017 01:34 AM, Richard Biener wrote: >> >> On Wed, Jan 4, 2017 at 8:24 PM, Jeff Law wrote: >>> >>> >>> The more I think about this the more I'm sure we need to verify pt.null >>> is >>> not in the points-to set.I've taken the above te

Re: [PR tree-optimization/67955] Exploit PTA in DSE

2017-01-07 Thread Jeff Law
On 01/05/2017 01:34 AM, Richard Biener wrote: On Wed, Jan 4, 2017 at 8:24 PM, Jeff Law wrote: The more I think about this the more I'm sure we need to verify pt.null is not in the points-to set.I've taken the above testcase and added it as a negative test. Bootstrapped, regression tested

Re: [PR tree-optimization/67955] Exploit PTA in DSE

2017-01-06 Thread Christophe Lyon
Hi Jeff, On 5 January 2017 at 09:34, Richard Biener wrote: > On Wed, Jan 4, 2017 at 8:24 PM, Jeff Law wrote: >> On 01/04/2017 11:55 AM, Jeff Law wrote: >>> >>> On 12/09/2016 01:28 AM, Richard Biener wrote: On Wed, Dec 7, 2016 at 12:18 AM, Jeff Law wrote: > > > > So I

Re: [PR tree-optimization/67955] Exploit PTA in DSE

2017-01-05 Thread Richard Biener
On Wed, Jan 4, 2017 at 8:24 PM, Jeff Law wrote: > On 01/04/2017 11:55 AM, Jeff Law wrote: >> >> On 12/09/2016 01:28 AM, Richard Biener wrote: >>> >>> On Wed, Dec 7, 2016 at 12:18 AM, Jeff Law wrote: So I was going through the various DSE related bugs as stumbled across 67

Re: [PR tree-optimization/67955] Exploit PTA in DSE

2017-01-04 Thread Jeff Law
On 01/04/2017 11:55 AM, Jeff Law wrote: On 12/09/2016 01:28 AM, Richard Biener wrote: On Wed, Dec 7, 2016 at 12:18 AM, Jeff Law wrote: So I was going through the various DSE related bugs as stumbled across 67955. The basic issue in 67955 is that DSE is too simplistic when trying to determin

Re: [PR tree-optimization/67955] Exploit PTA in DSE

2017-01-04 Thread Jeff Law
On 12/09/2016 01:28 AM, Richard Biener wrote: On Wed, Dec 7, 2016 at 12:18 AM, Jeff Law wrote: So I was going through the various DSE related bugs as stumbled across 67955. The basic issue in 67955 is that DSE is too simplistic when trying to determine if two writes hit the same memory addre

Re: [PR tree-optimization/67955] Exploit PTA in DSE

2016-12-09 Thread Richard Biener
On Wed, Dec 7, 2016 at 12:18 AM, Jeff Law wrote: > > > So I was going through the various DSE related bugs as stumbled across > 67955. > > The basic issue in 67955 is that DSE is too simplistic when trying to > determine if two writes hit the same memory address. There are cases were > PTA analys