Re: [PATCH] match: Undo maybe_push_res_to_seq in some cases [PR120331]

On Fri, May 23, 2025 at 2:39 AM Richard Biener wrote: > > On Thu, May 22, 2025 at 3:11 AM Jeff Law wrote: > > > > > > > > On 5/18/25 10:38 AM, Andrew Pinski wrote: > > > While working on improving forwprop and removal of > > > forward_propagate_into_gimple_cond/forward_propagate_into_comparison,

Re: [PATCH] match: Undo maybe_push_res_to_seq in some cases [PR120331]

On Thu, May 22, 2025 at 3:11 AM Jeff Law wrote: > > > > On 5/18/25 10:38 AM, Andrew Pinski wrote: > > While working on improving forwprop and removal of > > forward_propagate_into_gimple_cond/forward_propagate_into_comparison, > > I came cross a case where we end up with SSA_NAME in the resulting

Re: [PATCH] match: Undo maybe_push_res_to_seq in some cases [PR120331]

On 5/18/25 10:38 AM, Andrew Pinski wrote: While working on improving forwprop and removal of forward_propagate_into_gimple_cond/forward_propagate_into_comparison, I came cross a case where we end up with SSA_NAME in the resulting gimple_match_op and one statement in the sequence. This was the

[PATCH] match: Undo maybe_push_res_to_seq in some cases [PR120331]

While working on improving forwprop and removal of forward_propagate_into_gimple_cond/forward_propagate_into_comparison, I came cross a case where we end up with SSA_NAME in the resulting gimple_match_op and one statement in the sequence. This was the result of simplification of: ``` _3 = MIN_EXPR