This change removes the ad-hoc implementation used by llvm-xray's
convert subcommand to generate JSON encoded catapult (AKA Chrome
Trace Viewer) trace output, to instead use the JSON encoder now in the
Support library.
Details
Diff Detail
- Build Status
- Buildable 21029 - Build 21029: arc lint + arc unit 
Event Timeline
This is way easier to read now. Did you sanity check loading a trace into chrome trace viewer that it outputs?
| llvm/tools/llvm-xray/xray-converter.cpp | ||
|---|---|---|
| 282 | Strange that the code you're replacing changed the precision between 4 and 3 depending on the version. Four seems like a better choice and matches the behavior for version >= 3. | |
| 324 | Is it meaningful to have the trailing comma just before the end of the initializer list? I am kind of surprised to see that this works. | |
| 337 | What does {0:2} mean in this context? Is there a Json particular format provider? | |
Strange that the code you're replacing changed the precision between 4 and 3 depending on the version. Four seems like a better choice and matches the behavior for version >= 3.