Zachary Turner 94eade8938 [MSF] Default to FPM2, and always mark FPM pages allocated. ... There are two FPMs in an MSF file, the idea being that for incremental updates you can write to the alternate one and then atomically swap them on commit. LLVM defaulted to using FPM1 on the first commit, but this differs from Microsoft's behavior which is to default to using FPM2 on the first commit. To eliminate some byte-level file differences, this patch changes LLVM's default to also be FPM2. Additionally, LLVM was trying to be "smart" about marking FPM pages allocated. In addition to marking every page belonging to the alternate FPM as unallocated, LLVM also marked pages at the end of the main FPM which were not needed as unallocated. In order to match the behavior of Microsoft-generated PDBs, we now always mark every FPM block as allocated, regardless of whether it is in the main FPM or the alt FPM, and regardless of whether or not it describes blocks which are actually in the file. This has the side benefit of simplifying our code. llvm-svn: 328812		2018-03-29 18:34:15 +00:00
..
DIA
Inputs
Native
dbi-bytes.test
dump-fpm.test
every-type.test
just-my-code.test
module-bytes.test
module-stats.test
obj-globalhash.test	Regex out the local hash comparison test.	2017-12-06 00:58:12 +00:00
pdb-longname-truncation.test
pdb-minimal-construct.test
pdb-unknown-symbol.test
pdb-yaml-symbols.test
pdbdump-debug-subsections.test
pdbdump-globals-empty.test
pdbdump-headers.test
pdbdump-merge-ids-and-types.test
pdbdump-mergeids.test
pdbdump-mergetypes.test
pdbdump-objfilename.yaml
pdbdump-raw-blocks.test
pdbdump-raw-bytes.test
pdbdump-raw-stream.test
pdbdump-readwrite.test
pdbdump-source-names.test
pdbdump-write.test
pdbdump-yaml-types.test
pdbdump-yaml.test
section-headers.test
tpi-bytes.test
udt-stats.test
write-fpm.test	[MSF] Default to FPM2, and always mark FPM pages allocated.	2018-03-29 18:34:15 +00:00