Hi,
How are MIR passes supposed to deal with custom state tracked in the target’s MachineFunctionInfo? I’m trying to test a patch which checks a bit set in it during register allocation. If I just run the post-RA pass which checks it, it was never set in the newly constructed one. I’d rather not have every pass need to re-analyze some possibly tricky to detect situation to avoid using it
-Matt
Hi,
How are MIR passes supposed to deal with custom state tracked in the
target’s MachineFunctionInfo? I’m trying to test a patch which checks a bit
set in it during register allocation. If I just run the post-RA pass which
checks it, it was never set in the newly constructed one. I’d rather not
have every pass need to re-analyze some possibly tricky to detect situation
to avoid using it
Hi Matt,
I haven't looked into MIR since last year, so maybe this has changed, but
AFAIK there's no way to serialize target's custom machine function info
state. I think I was working on patches that allowed targets to serialize
custom machine function information using MIR before I finished my
internship, so I'll try to dig them up again.
Alex