LLVM with the emscripten fastcomp javascript backend https://git.amat.us/emscripten-fastcomp/atom/include/llvm/Bitcode/NaCl?h=master 2013-11-21T18:34:00Z 2013-11-21T18:34:00Z Karl Schimpf kschimpf@google.com 2013-11-21T18:34:00Z urn:sha1:7026af7138fccfb256456b04b375d39b025bdb7c Write out all of PNaCl bitcode headers using a single interface function. BUG= https://code.google.com/p/nativeclient/issues/detail?id=3720 R=jvoung@chromium.org Review URL: https://codereview.chromium.org/61753017 2013-11-21T17:40:15Z Karl Schimpf kschimpf@google.com 2013-11-15T21:47:14Z urn:sha1:757414ba931360b0c65851c2583e511d67948d91 Define comparison of bitcode abbreviations so that we can add bitcode abbreviations to collections. BUG= https://code.google.com/p/nativeclient/issues/detail?id=3720 2013-11-07T16:54:33Z Karl Schimpf kschimpf@google.com 2013-11-07T16:54:33Z urn:sha1:2796c5b8a31ea88cc24bf3449a95319928c93519 Factors out bitcode parser from pnacl-bcanalyzer, so that it can also be used for PNaCl bitcode to bitcode rewriters. BUG= https://code.google.com/p/nativeclient/issues/detail?id=3720 R=jvoung@chromium.org Review URL: https://codereview.chromium.org/48623003 2013-10-03T15:08:25Z Mark Seaborn mseaborn@chromium.org 2013-10-03T15:08:25Z urn:sha1:8ed96f4d0ca9b8114875997f1f0196fc89a41a04 Make the reader and writer stricter so that we can be sure we're not accidentally generating ptrtoint or inttoptr instructions in pexe files. BUG=https://code.google.com/p/nativeclient/issues/detail?id=3590 TEST=toolchain trybots Review URL: https://codereview.chromium.org/25607006 2013-09-18T21:24:56Z Karl Schimpf kschimpf@google.com 2013-09-18T21:24:56Z urn:sha1:197cadba6026114ce62ed57dafe2125e70500a6b BUG= https://code.google.com/p/nativeclient/issues/detail?id=3590 R=mseaborn@chromium.org Review URL: https://codereview.chromium.org/24232002 2013-09-13T21:29:09Z Derek Schuff dschuff@chromium.org 2013-09-13T21:29:09Z urn:sha1:f8cb03fe2634ee927b3b6aa6ecbdd824cd0bc940 Install a fatal error handler for the translator, which stores the error string, signals an error to the RPC thread, and terminates the thread (instead of terminating the whole program). This will cause the error to go to the Javascript console in Chrome BUG= https://code.google.com/p/nativeclient/issues/detail?id=3519 R=jvoung@chromium.org Review URL: https://codereview.chromium.org/23753003 2013-09-06T20:27:38Z Karl Schimpf kschimpf@google.com 2013-09-06T20:27:38Z urn:sha1:9b86d1e242fec1dce22eda36b8f2eb3d6f1cc380 * Removes code that is no longer used because global variables are handled separately. * Removes CST_CODE_NULL. * Adds special abbreviations for constant integer 0, replacing most of what was lost when CST_CODE_NULL is removed. * Adds abbreviation for floating point constants. * Removes CST_CODE_AGGREGATE and CST_CODE_DATA, except for reading old PNaCl version 1 bitcode files. * Removes call to ParseConstants() in ParseModule() since the module block no longer contains a constants block (globals are handled separately). * Removes getConstantFwdRef() method, since it is no longer needed. * Remove ConstantPlaceHolder class, since it is no longer needed. * Remove ResolvedConstants and ResolveConstantForwardRefs() from the bitcode reader, since it is no longer needed. BUG= https://code.google.com/p/nativeclient/issues/detail?id=3668 R=mseaborn@chromium.org Review URL: https://codereview.chromium.org/23522024 2013-09-05T16:41:53Z Mark Seaborn mseaborn@chromium.org 2013-09-05T16:41:53Z urn:sha1:cd4a14419f49fb236d65e5b69d871d6fc61fcb99 For indirect call instructions (INST_CALL_INDIRECT), it's not necessary to store the full function type. The argument types are already known from the arguments in the instruction. We only need to store the return type to be able to reconstruct the full function type. Storing only the return type ID will make the bitcode a little more compact. Return type IDs will be frequently-used scalar types, which can be given smaller type IDs than function types, which are less frequently used. This potentially makes the writer simpler: In principle, the writer no longer needs to make a pass across all functions' bodies to determine which function types are used in order to build the type table. BUG=https://code.google.com/p/nativeclient/issues/detail?id=3544 TEST=*.ll tests Review URL: https://codereview.chromium.org/23521005 2013-09-05T15:46:41Z Mark Seaborn mseaborn@chromium.org 2013-09-05T15:46:41Z urn:sha1:1180f259c88b1eb1000d0aaf5753b3da9f8e4e51 The type ID for the "label" type is never referenced. The "label" type was only being added to the type table because EnumerateType() treats BasicBlock and Value operands the same. However, the rest of the reader and writer treat BasicBlock operands specially and not like other Values. Change some tests to use wildcards for some type IDs. This is so that I don't have to update all the type ID numbers now that the generated type tables have changed. BUG=https://code.google.com/p/nativeclient/issues/detail?id=3590 TEST=run small_tests with v2 bitcode format enabled Review URL: https://codereview.chromium.org/23530031 2013-09-04T20:34:52Z Karl Schimpf kschimpf@google.com 2013-09-04T20:34:52Z urn:sha1:d8f9bfbc093e7e0c1fab719bc014ba7c6f94ad6d The value selector list for switch statements are represented using ARRAY/VECTOR constants, but this information is not put into the bitcode file. This CL changes the value enumerator to not emit these constants. BUG= https://code.google.com/p/nativeclient/issues/detail?id=3649 R=mseaborn@chromium.org Review URL: https://codereview.chromium.org/23653013