public Processor getProcessor() {
		return processor;
	}
Machine Type seen in the {@link PdbNewDebugInfo} header.  We also map in the Processor.
We are not exactly sure about why there are different but similar items: Machine Type and
Processor.  The {@link Processor} is what is specified in {@link AbstractCompile2MsSymbol} and
{@link Compile3MsSymbol} and what we save off in {@link AbstractPdb}, but
{@link ImageFileMachine} is what we see in the header of {@link PdbNewDebugInfo}.
@see <a href="https://docs.microsoft.com/en-us/windows/desktop/sysinfo/image-file-machine-constants">
Image File Machine Constants</a>
@see <a href="http://metadataconsulting.blogspot.com/2014/06/imagefilemachine-extensive-machine-type.html">
Also Image File Machine Constants</a>
@see <a href="https://docs.microsoft.com/en-us/windows/desktop/api/winnt/ns-winnt-image_file_header">
Other use</a>
Ghidra/Features/PDB/src/main/java/ghidra/app/util/bin/format/pdb2/pdbreader/ImageFileMachine.java