Re: operand_equal_p() and SSA_NAME

2017-08-28 Thread Jeff Law
On 08/28/2017 09:46 PM, Andrew Pinski wrote: > On Mon, Aug 28, 2017 at 7:46 PM, Martin Sebor wrote: >> operand_equal_p() doesn't handle SSA_NAMEs and returns false for >> operands in that form even when they have equal values (when both >> are ADDR_EXPR of the same decl). Yet the function is exte

Re: operand_equal_p() and SSA_NAME

2017-08-28 Thread Jeff Law
On 08/28/2017 08:46 PM, Martin Sebor wrote: > operand_equal_p() doesn't handle SSA_NAMEs and returns false for > operands in that form even when they have equal values (when both > are ADDR_EXPR of the same decl). Yet the function is extensively > relied on in the middle end where I would expect i

Re: operand_equal_p() and SSA_NAME

2017-08-28 Thread Andrew Pinski
On Mon, Aug 28, 2017 at 7:46 PM, Martin Sebor wrote: > operand_equal_p() doesn't handle SSA_NAMEs and returns false for > operands in that form even when they have equal values (when both > are ADDR_EXPR of the same decl). Yet the function is extensively > relied on in the middle end where I woul

operand_equal_p() and SSA_NAME

2017-08-28 Thread Martin Sebor
operand_equal_p() doesn't handle SSA_NAMEs and returns false for operands in that form even when they have equal values (when both are ADDR_EXPR of the same decl). Yet the function is extensively relied on in the middle end where I would expect it be beneficial to have it handle SSA_NAMEs. At a