Hi, First question: Has anyone ever employed Simpoint to parse a bbv.gz file and generate simpoints and weights, what measures can be taken to avoid having simpoint generated from the instruction 0? like this: [cid:image001.png@01D989A6.4706BA60] Second question: After I created a gem5 checkpoint using simpoints(instruction 0), the restoration process failed to run properly and stat.txt contained no valid information. The command used to generate the checkpoint is as follows: ./build/RISCV/gem5.fast --outdir ./m5out/out_cpt_test configs/example/se.py \ --take-simpoint-checkpoint simpoint_file,weight_file,100000000,1000000 \ --cpu-type=RiscvNonCachingSimpleCPU \ -c hmmer_base.gcc43-64bit --options="nph3.hmm swiss41" Result of generation: [cid:image002.png@01D989A6.FD2EF5F0] The command used for restoration is as follows: ./build/RISCV/gem5.fast --outdir m5out/test/ configs/example/se.py \ --mem-size 1GB --cpu-type RiscvTimingSimpleCPU \ -c hmmer_base.gcc43-64bit -o "nph3.hmm swiss41" \ --restore-simpoint-checkpoint -r 1 --checkpoint-dir m5out/out_cpt_test/ Result of restoration: [cid:image003.png@01D989A7.D1D744B0] stat.txt: [cid:image004.png@01D989A8.1B4925F0] should it not execute 100000000 insts? BR, yu