I think ReplayDataFile can overwrite where to write a replay file. Currently, it can only rule VMError::report_and_die(), where a compiler thread has a severe error.

  product(ccstr, ReplayDataFile, NULL, \
          "File containing compilation replay information" \
          "[default: ./replay_pid%p.log] (%p replaced with pid)") \


In compiler directive, DumpReplay is a handy directive to let JIT compiler dump a closure of a compilation. It's useful for developers to study an individual compilation offline. Now it writes to CWD only.

Sometimes, it's really inconvenient to preserve CWD files. eg. openjdk "make test" doesn't save any "replay_pid%d_compid%d.log". Docker and serverless environments are other scenarios in general.

I am thinking about let ciEnv::dump_replay_data() considers ReplayDataFile.
if compile_id is an important component, we can also add "%c" and substitute it with current compile_id.