Hi ChampSim team,
First of all, thank you for providing and maintaining ChampSim — it is a very helpful tool for research and teaching in microarchitecture.
I am currently experimenting with the --wrong-path and --wpa modes in ChampSim. While these options are supported in the simulator, I could not find documentation on how to generate or preprocess wrong-path traces that can be used effectively with these modes.
Feature request
Could you please provide guidance or documentation on:
How to construct traces that contain wrong-path information (e.g., how to mark flags or pref in the input trace format)?
If there are recommended tools, scripts, or trace-generation workflows to extract this information from real executions.
(Optional) Example traces with wrong-path annotations for validation.
This would be very useful for researchers who want to study wrong-path execution, WPA mechanisms, or related microarchitectural optimizations.
Motivation
Right now, the simulator can switch between CP/WP/WPA modes, but without wrong-path–aware trace data, it is not straightforward to validate or compare these modes. Having clear instructions or sample workflows would make it much easier for new users to leverage this feature.
Thank you for your time and for considering this request!
Hi ChampSim team,
First of all, thank you for providing and maintaining ChampSim — it is a very helpful tool for research and teaching in microarchitecture.
I am currently experimenting with the --wrong-path and --wpa modes in ChampSim. While these options are supported in the simulator, I could not find documentation on how to generate or preprocess wrong-path traces that can be used effectively with these modes.
Feature request
Could you please provide guidance or documentation on:
How to construct traces that contain wrong-path information (e.g., how to mark flags or pref in the input trace format)?
If there are recommended tools, scripts, or trace-generation workflows to extract this information from real executions.
(Optional) Example traces with wrong-path annotations for validation.
This would be very useful for researchers who want to study wrong-path execution, WPA mechanisms, or related microarchitectural optimizations.
Motivation
Right now, the simulator can switch between CP/WP/WPA modes, but without wrong-path–aware trace data, it is not straightforward to validate or compare these modes. Having clear instructions or sample workflows would make it much easier for new users to leverage this feature.
Thank you for your time and for considering this request!