Several profiling tests give different results optimised vs. unoptimised
Most of the differences are relatively harmless (mostly CAF attribution), but it would be nice to get this right. In the meantime I'll mark them expect_broken and point to this ticket.
The following tests in
tests/profiling/should_run are affected:
scc001 T2552 ioprof callstack001