You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the files generated by rustc -Zself-profile don't contain any indication of what their concrete encoding is. That should change so that post-processing tools support more than one version or at least give a sensible error message when encountering an unsupported encoding.
For example, each file could start with a some file magic (b"MMES" for the event stream, b"MMSD" for the string table data, and b"MMSI" for the string table index) and a 4 byte little-endian version number that can be used to select the right decoder.
The text was updated successfully, but these errors were encountered:
Right now the files generated by
rustc -Zself-profile
don't contain any indication of what their concrete encoding is. That should change so that post-processing tools support more than one version or at least give a sensible error message when encountering an unsupported encoding.For example, each file could start with a some file magic (
b"MMES"
for the event stream,b"MMSD"
for the string table data, andb"MMSI"
for the string table index) and a 4 byte little-endian version number that can be used to select the right decoder.The text was updated successfully, but these errors were encountered: