Closed Elarnon closed 5 years ago
Previously we were generating a
best_X.c
andbest_X.cfg
for each best candidate, which doesn't allow to easily re-use the found implementation e.g. in the debugger. Thetlcli rebuild
command was introduced for this purpose, and can extract a replay file from the eventlog.However, evenlogs these days tend to be quite large, and it may not be
eventlogs
desirable to keep them for runs which don't need specific performance analysis. Hence, this patch changes the mechanism for dumping best candidates: now a directory
best_X
is created, with the generated code incode.c
; the loop tree incode.cfg
; and the replay inactions.json
(not unlike the format used for errors, which also contain extra files about the error).
Previously we were generating a
best_X.c
andbest_X.cfg
for each best candidate, which doesn't allow to easily re-use the found implementation e.g. in the debugger. Thetlcli rebuild
command was introduced for this purpose, and can extract a replay file from the eventlog.However, evenlogs these days tend to be quite large, and it may not be desirable to keep them for runs which don't need specific performance analysis. Hence, this patch changes the mechanism for dumping best candidates: now a directory
best_X
is created, with the generated code incode.c
; the loop tree incode.cfg
; and the replay inactions.json
(not unlike the format used for errors, which also contain extra files about the error).