The EntityVariable materializer was, under certain conditions, taking the bytes of a DataExtractor that were potentially in host order (e.g. little endian) and putting them in the IRMemoryMap (which assumes all values are in target order, e.g. big endian). This caused certain values to have the wrong endianness during expression evaluation.
On our platform, this manifested as certain expressions yielding incorrect results when the variables were in registers (e.g. argc + 1 would give 0x01000001).