Skip to content

Commit a6e8106

Browse files
committed
> What is UID in this context? Should this be PID?
I have changed this to be `PID`. Note that I expect the naming strategy to change in the future as we get feedback from more distribution systems. I have some concerns that mixing the PID into the filenames might prevent the caching systems for some distribution systems from working effectively.
1 parent a828b70 commit a6e8106

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

llvm/docs/DTLTO.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -112,15 +112,15 @@ include the stem of the bitcode module, or the output file that the LTO
112112
invocation is contributing to, to aid the user in identifying them:
113113

114114
- **JSON Job Description File**:
115-
- Format: `dtlto.<UID>.dist-file.json`
115+
- Format: `dtlto.<PID>.dist-file.json`
116116
- Example: `dtlto.77380.dist-file.json` (for output file `dtlto.elf`).
117117

118118
- **Object Files From Backend Compilations**:
119-
- Format: `<Module ID stem>.<Task>.<UID>.native.o`
119+
- Format: `<Module ID stem>.<Task>.<PID>.native.o`
120120
- Example: `my.1.77380.native.o` (for bitcode module `my.o`).
121121

122122
- **Summary Index Shard Files**:
123-
- Format: `<Module ID stem>.<Task>.<UID>.native.o.thinlto.bc`
123+
- Format: `<Module ID stem>.<Task>.<PID>.native.o.thinlto.bc`
124124
- Example: `my.1.77380.native.o.thinlto.bc` (for bitcode module `my.o`).
125125

126126
Temporary files are removed, by default, after the backend compilations complete.

0 commit comments

Comments
 (0)