Displaying 3 results from an estimated 3 matches for "56c04fdd".
2013 Jun 18
0
[LLVMdev] Building a stable bitcode format for PNaCl - based on LLVM IR
Instead of a blacklist, why not a whitelist? Given the size of LangRef,
you're bound to leave something out of your blacklist that needs to be
there (also, future additions to LLVM IR will need to be added to the
blacklist; are you sure you can catch *all* of them?). A whitelist seems
much less prone to breakage or unexpected behavior.
-- Sean Silva
-------------- next part --------------
An
2013 Jun 18
3
[LLVMdev] Building a stable bitcode format for PNaCl - based on LLVM IR
...ecifically
allow or disallow certain constructs (such as specific instructions,
intrinsics, linkage modes and so on) we use a whitelisting strategy.
Eli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130618/56c04fdd/attachment.html>
2013 Jun 18
6
[LLVMdev] Building a stable bitcode format for PNaCl - based on LLVM IR
Hello,
[The first paragraph is safe to skip if you already know what PNaCl is.]
The Portable Native Client (PNaCl) project is a toolchain for producing
portable bitcode from C and C++ code and running in securely and
efficiently on the web via Native Client. For more details see this
presentation from the last Google I/O:
https://developers.google.com/events/io/sessions/325679543and