On 5/23/25 12:22 PM, Vineet Gupta wrote:
3. NOK: We loose the ability to instrument local RM writes - especially in the
testsuite.
e.g.
a. instrinsic setting a static RM
b. get_frm() to ensure that happened (inline asm to read out frm)
The tightly coupled restore kicks in before get_frm could be emitted which fails
to observe #a. This is a deal breaker for the testsuite as much of frm tests
report as fail even if the actual codegen is sane.
I must be missing something here, but ISTM that if testsuite
observability is the only show stopper, then we can likely do something
here.
Rather than using get_frm, could we use an old style asm that doesn't
expose FRM implications? We'd need to make sure it's ordered WRT the
actual FRM operations we care about. But maybe that would be possible
with a few well placed optimization barriers.
Anyway, just thinking out load.
jeff
