3 ms·
Right. I had always thought that LLVM bitcode was unsuitable as a portable representation because it inevitably encoded architecture-specific details. Consider
by millstone 13y ago
Right. I had always thought that LLVM bitcode was unsuitable as a portable representation because it inevitably encoded architecture-specific details.
Consider code like this:
int lsize(void) { return sizeof(void *); }
how would this be compiled portably, so that it returns 4 or 8 as appropriate? What would the LLVM bitcode look like?
- jensnockert 13y agoThis is true for LLVM bitcode in general, but PNaCl specifies an abstract machine that defines pointers as 4 bytes long. It also specifies Little Endian &c. See http://www.chromium.org/nativeclient/pnacl/bitcode-abi#TOC-Data-Types http://www.chromium.org/nativeclient/pnacl/bitcode-abi#TOC-D...