I think this makes sense to implement. Another alternative that we discussed offline was adding a flag to switch whether we’re emitting information from the BFI/BPI analyses or from the Propeller profile. That would have the advantage of not requiring any new encoding/decoding support and not using up an additional feature bit. However, we lose a lot of convenience if we want both PGO and Propeller data, which would be useful in a lot of scenarios where PGOAnalysisMap is currently used. We would need to do two builds which can be pretty expensive, especially since they would be completely identical minus the profile data that gets embedded in the binary. Being able to easily compare the two profiles would be very useful for checking profile fidelity.