Re: [PATCH] Fix segfault in FRE during SCC value numbering

2014-01-15 Thread Teresa Johnson
I did try disabling early inlining and some other things but still didn't have luck. The indirect call promotion is also in a different phase in trunk and google/4_8, which was adding another complication. Teresa On Wed, Jan 15, 2014 at 1:23 PM, Xinliang David Li wrote: > There are options you ca

Re: [PATCH] Fix segfault in FRE during SCC value numbering

2014-01-15 Thread Xinliang David Li
There are options you can use to control passes explicitly: -fdisable-... -fenable- To disable early inline: -fdisable-tree-einline David On Wed, Jan 15, 2014 at 1:17 PM, Teresa Johnson wrote: > On Wed, Jan 15, 2014 at 12:00 PM, Teresa Johnson wrote: >> On Wed, Jan 15, 2014 at 10:46 AM, J

Re: [PATCH] Fix segfault in FRE during SCC value numbering

2014-01-15 Thread Teresa Johnson
On Wed, Jan 15, 2014 at 12:00 PM, Teresa Johnson wrote: > On Wed, Jan 15, 2014 at 10:46 AM, Jeff Law wrote: >> On 01/15/14 10:07, Teresa Johnson wrote: >>> >>> Handle NULL vdef for call in the case where we have a matching vnresult >>> that has a vdef (it already handles the NULL vdef case when !

Re: [PATCH] Fix segfault in FRE during SCC value numbering

2014-01-15 Thread Teresa Johnson
On Wed, Jan 15, 2014 at 10:46 AM, Jeff Law wrote: > On 01/15/14 10:07, Teresa Johnson wrote: >> >> Handle NULL vdef for call in the case where we have a matching vnresult >> that has a vdef (it already handles the NULL vdef case when !vnresult). >> This >> can happen for promoted indirect calls if

Re: [PATCH] Fix segfault in FRE during SCC value numbering

2014-01-15 Thread Jeff Law
On 01/15/14 10:07, Teresa Johnson wrote: Handle NULL vdef for call in the case where we have a matching vnresult that has a vdef (it already handles the NULL vdef case when !vnresult). This can happen for promoted indirect calls if the fallback indirect call (which has a vdef) can be proven equiv

[PATCH] Fix segfault in FRE during SCC value numbering

2014-01-15 Thread Teresa Johnson
Handle NULL vdef for call in the case where we have a matching vnresult that has a vdef (it already handles the NULL vdef case when !vnresult). This can happen for promoted indirect calls if the fallback indirect call (which has a vdef) can be proven equivalent to the promoted direct call (which mi