Skip to content
  1. Mar 21, 2017
    • Serge Pavlov's avatar
      Fix evaluation of LLVM_DEFINITIONS · 23be9459
      Serge Pavlov authored
      CMake variable LLVM_DEFINITIONS collects preprocessor definitions provided
      for host compiler that builds llvm components. A function
      add_llvm_definitions was introduced in AddLLVMDefinitions.cmake to keep
      track of these definitions and was intended to be a replacement for CMake
      command add_definitions. Actually in many cases add_definitions is still
      used and the content of LLVM_DEFINITIONS is not actual now. On the other
      hand the current version of CMake allows getting set of definitions in a
      more convenient way. This fix implements evaluation of the variable by
      reading corresponding cmake property.
      
      Differential Revision: https://reviews.llvm.org/D31125
      
      llvm-svn: 298336
      23be9459
    • Vitaly Buka's avatar
      Revert "[Hexagon] Recognize polynomial-modulo loop idiom again" · c12716e7
      Vitaly Buka authored
      Fix memory leaks on check-llvm tests detected by Asan.
      
      This reverts commit r298282.
      
      llvm-svn: 298329
      c12716e7
    • Eli Friedman's avatar
      [ARM] Revert r297443 and r297820. · 76732acc
      Eli Friedman authored
      The glueless lowering of addc/adde in Thumb1 has known serious
      miscompiles (see https://reviews.llvm.org/D31081), and r297820
      causes an infinite loop for certain constructs.  It's not
      clear when they will be fixed, so let's just take them out
      of the tree for now.
      
      (I resolved a small conflict with r297453.)
      
      llvm-svn: 298328
      76732acc
    • Zachary Turner's avatar
      [Support] Fill the file_status struct with link count. · 5821a3bf
      Zachary Turner authored
      Differential Revision: https://reviews.llvm.org/D31110
      
      llvm-svn: 298326
      5821a3bf
    • Zachary Turner's avatar
      Add a function to MD5 a file's contents. · 82a0c97b
      Zachary Turner authored
      In doing so, clean up the MD5 interface a little.  Most
      existing users only care about the lower 8 bytes of an MD5,
      but for some users that care about the upper and lower,
      there wasn't a good interface.  Furthermore, consumers
      of the MD5 checksum were required to handle endianness
      details on their own, so it seems reasonable to abstract
      this into a nicer interface that just gives you the right
      value.
      
      Differential Revision: https://reviews.llvm.org/D31105
      
      llvm-svn: 298322
      82a0c97b
  2. Mar 20, 2017
Loading