tree 43238924de749af27cba6921876f5e8fe14f2be9
parent 1f89469f300e7a4304b1d85a39f90114ae8dc8ff
author Zachary Turner <zturner@google.com> 1542336152 +0000
committer Zachary Turner <zturner@google.com> 1542336152 +0000

[NativePDB] Rewrite the PdbSymUid to use our own custom namespacing scheme.

Originally we created our 64-bit UID scheme by using the first byte as
sort of a "tag" to represent what kind of symbol this was, and we
re-used the PDB_SymType enumeration for this.  For native pdb support,
this is not really the right abstraction layer, because what we really
want is something that tells us *how* to find the symbol.  This means,
specifically, is in the globals stream / public stream / module stream /
TPI stream / etc, and for whichever one it is in, where is it within
that stream?

A good example of why the old namespacing scheme was insufficient is
that it is more or less impossible to create a uid for a field list
member of a class/struction/union/enum that tells you how to locate
the original record.

With this new scheme, the first byte is no longer a PDB_SymType enum
but a new enum created specifically to identify where in the PDB
this record lives.  This gives us much better flexibility in
what kinds of symbols the uids can identify.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@347018 91177308-0d34-0410-b5e6-96231b3b80d8