Skip to content
  1. Jan 12, 2009
  2. Jan 07, 2009
  3. Nov 13, 2008
  4. Sep 25, 2008
    • Devang Patel's avatar
      Large mechanical patch. · 4c758ea3
      Devang Patel authored
      s/ParamAttr/Attribute/g
      s/PAList/AttrList/g
      s/FnAttributeWithIndex/AttributeWithIndex/g
      s/FnAttr/Attribute/g
      
      This sets the stage 
      - to implement function notes as function attributes and 
      - to distinguish between function attributes and return value attributes.
      
      This requires corresponding changes in llvm-gcc and clang.
      
      llvm-svn: 56622
      4c758ea3
  5. Jul 30, 2008
  6. Jun 06, 2008
    • Duncan Sands's avatar
      Wrap MVT::ValueType in a struct to get type safety · 13237ac3
      Duncan Sands authored
      and better control the abstraction.  Rename the type
      to MVT.  To update out-of-tree patches, the main
      thing to do is to rename MVT::ValueType to MVT, and
      rewrite expressions like MVT::getSizeInBits(VT) in
      the form VT.getSizeInBits().  Use VT.getSimpleVT()
      to extract a MVT::SimpleValueType for use in switch
      statements (you will get an assert failure if VT is
      an extended value type - these shouldn't exist after
      type legalization).
      This results in a small speedup of codegen and no
      new testsuite failures (x86-64 linux).
      
      llvm-svn: 52044
      13237ac3
  7. Jan 04, 2008
  8. Jan 02, 2008
  9. Dec 29, 2007
  10. Dec 17, 2007
  11. Dec 03, 2007
  12. Sep 28, 2007
  13. Aug 16, 2007
  14. Aug 06, 2007
  15. Aug 04, 2007
    • Chandler Carruth's avatar
      This is the patch to provide clean intrinsic function overloading support in... · 7132e00d
      Chandler Carruth authored
      This is the patch to provide clean intrinsic function overloading support in LLVM. It cleans up the intrinsic definitions and generally smooths the process for more complicated intrinsic writing. It will be used by the upcoming atomic intrinsics as well as vector and float intrinsics in the future.
      
      This also changes the syntax for llvm.bswap, llvm.part.set, llvm.part.select, and llvm.ct* intrinsics. They are automatically upgraded by both the LLVM ASM reader and the bitcode reader. The test cases have been updated, with special tests added to ensure the automatic upgrading is supported.
      
      llvm-svn: 40807
      7132e00d
  16. Jul 26, 2007
  17. Jun 26, 2007
  18. May 22, 2007
  19. Apr 16, 2007
    • Reid Spencer's avatar
      For PR1328: · 9c2eec37
      Reid Spencer authored
      Don't assert everytime an intrinsic name isn't recognized. Instead, make
      the assert optional when callin getIntrinsicID(). This allows the assembler
      to handle invalid intrinsic names gracefully.
      
      llvm-svn: 36120
      9c2eec37
  20. Apr 01, 2007
    • Reid Spencer's avatar
      For PR1297: · e67d0c22
      Reid Spencer authored
      Implement code generation for overloaded intrinsic functions. The basic
      difference is that "actual" argument types must be provided when
      constructing intrinsic names and types. Also, for recognition, only the
      prefix is examined. If it matches, the suffix is assumed to match. The
      suffix is checked by the Verifier, however.
      
      llvm-svn: 35539
      e67d0c22
  21. Feb 15, 2007
  22. Feb 07, 2007
  23. Feb 06, 2007
  24. Jan 12, 2007
    • Reid Spencer's avatar
      For PR1064: · 7a9c62ba
      Reid Spencer authored
      Implement the arbitrary bit-width integer feature. The feature allows
      integers of any bitwidth (up to 64) to be defined instead of just 1, 8,
      16, 32, and 64 bit integers.
      
      This change does several things:
      1. Introduces a new Derived Type, IntegerType, to represent the number of
         bits in an integer. The Type classes SubclassData field is used to
         store the number of bits. This allows 2^23 bits in an integer type.
      2. Removes the five integer Type::TypeID values for the 1, 8, 16, 32 and
         64-bit integers. These are replaced with just IntegerType which is not
         a primitive any more.
      3. Adjust the rest of LLVM to account for this change.
      
      Note that while this incremental change lays the foundation for arbitrary
      bit-width integers, LLVM has not yet been converted to actually deal with
      them in any significant way. Most optimization passes, for example, will
      still only deal with the byte-width integer types.  Future increments
      will rectify this situation.
      
      llvm-svn: 33113
      7a9c62ba
  25. Oct 04, 2006
  26. Apr 02, 2006
  27. Mar 31, 2006
  28. Mar 29, 2006
  29. Mar 24, 2006
Loading