News for hackers. Stuff that matters.
Re:Google Introduces Portable Native Client by millstone on Saturday May 18, 2013 @03:42AM (#5728197)
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?
Re:Google Introduces Portable Native Client by jensnockert on Saturday May 18, 2013 @03:50AM (#5728207)
This 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-D...