To make it possible to dump multiple objects during a single run, the
output files are named /path/to/snippet-OPCODE-REPETITOR.o with constant
parts omitted (for example, if dumping a single object file, its name is
exactly the value of --dump-object-to-disk option).
In dbc76ef791, the call to writeObjectFile() function was moved to
runConfiguration() because the latter is inherently serial to make the
"Check generated assembly with: ..." lines readable. Because now file
names are predictable, this message is not needed anymore, so the
writeObjectFile() function can be called at any suitable place.
~~
Huawei RRI, OS Lab
Why not always add the OPCODE and REPETITOR parts ? Consistency is good :)