| commit | 20bed3bb3579d581b909e2319523331cd76bca57 | [log] [tgz] |
|---|---|---|
| author | Jan Beulich <jbeulich@suse.com> | Thu May 19 12:45:55 2022 +0200 |
| committer | Jan Beulich <jbeulich@suse.com> | Thu May 19 12:45:55 2022 +0200 |
| tree | fe1f421b9587443ffcf3e23b8266e1c112f7d80d | |
| parent | f0a53c9c89316a0e362fd671f566f453e451b21c [diff] |
COFF: use hash for string table also when copying / stripping Otherwise the string table may grow and hence e.g. change a final binary (observed with PE/COFF ones) even if really there's no change. Doing so in fact reduces the overall amount of code, and in particular the number of places which need to remain in sync. Afaics there's no real equivalent to the "traditional_format" field used when linking, so hashing is always enabled when copying / stripping.