BOLT's assumption regarding data to code relocations is that
they will be "consumed", or accounted for, as jump table entries.
For jump tables that we failed to recognize, the relocation would
still be created and later attempted to be emitted, but if the
symbol was removed, this leads to undefined symbol error.
Add a post-processing step that accounts for such unclaimed
relocations and creates secondary entry points.
Are you tied to unordered_set ? There are more memory-efficient data structures:
https://llvm.org/docs/ProgrammersManual.html#set-like-containers-std-set-smallset-setvector-etc