The bitcode from Pnacl is different from the LLVM one..

But the "portable" backend naming scheme maybe could mean they will use the PNacl-LLVM instead of the pure LLVM one..

I wonder how Chrome could glue with this.. but if the Nacl/Pnacl uses the PPAPI api, in this hypotethical scenario they would replace the PPAPI runtime with a runtime compatible with ART..

it can be done, and the final c++ application source code would look like the java one..

edit: This could also mean the ndk applications will be first class citizens and wont need to rely on a java shim + native bindings.. I think that is more likely than the ChromeOS integration scenario