On Fri, Jul 18, 2025 at 11:42:59AM -0600, Jeff Law wrote: > > > On 7/18/25 11:03 AM, Artemiy Volkov wrote: > > On Wed, Jul 02, 2025 at 08:15:40PM -0600, Jeff Law wrote: > > > A number of folks have had their fingers in this code and it's going to > > > take > > > a few submissions to do everything we want to do. > > > > > > This patch is primarily concerned with avoiding signaling that fusion can > > > occur in cases where it obviously should not be signaling fusion. > > > > Hi Jeff, > > > > With this change, we're liable to ICE whenever prev_set or curr_set are > > NULL_RTX. For a fix, how about something like the below? > Sure. Do you have commit privs in the repo? If so this is OK once > pre-commit testing confirms there aren't any regressions. > > Did this trigger with the other work you're doing? Or was things something > you saw without our ongoing fusion work?
This isn't currently visible even with the full dejagnu run, I was only able to trigger this with my fusion patches which I'm currently preparing for upstreaming. I don't have commit access, so could you please push this to the trunk on my behalf? Thanks, Artemiy > > jeff
