Skip to content
  1. Dec 29, 2007
  2. Dec 25, 2007
  3. Dec 21, 2007
    • Duncan Sands's avatar
      Make DAE not wipe out attributes on calls, and not drop · 6a7703ed
      Duncan Sands authored
      return attributes on the floor.  In the case of a call
      to a varargs function where the varargs arguments are
      being removed, any call attributes on those arguments
      need to be dropped.  I didn't do this because I plan to
      make it illegal to have such attributes (see next patch).
      With this change, compiling the gcc filter2 eh test at -O0
      and then running opt -std-compile-opts on it results in
      a correctly working program (compiling at -O1 or higher
      results in the test failing due to a problem with how we
      output eh info into the IR).
      
      llvm-svn: 45285
      6a7703ed
  4. Dec 19, 2007
  5. Dec 18, 2007
  6. Dec 17, 2007
  7. Dec 10, 2007
  8. Dec 03, 2007
  9. Nov 27, 2007
    • Duncan Sands's avatar
      Fix PR1146: parameter attributes are longer part of · ad0ea2d4
      Duncan Sands authored
      the function type, instead they belong to functions
      and function calls.  This is an updated and slightly
      corrected version of Reid Spencer's original patch.
      The only known problem is that auto-upgrading of
      bitcode files doesn't seem to work properly (see
      test/Bitcode/AutoUpgradeIntrinsics.ll).  Hopefully
      a bitcode guru (who might that be? :) ) will fix it.
      
      llvm-svn: 44359
      ad0ea2d4
  10. Nov 22, 2007
  11. Nov 15, 2007
  12. Nov 14, 2007
  13. Nov 13, 2007
  14. Nov 09, 2007
  15. Nov 05, 2007
  16. Nov 04, 2007
  17. Nov 01, 2007
    • Duncan Sands's avatar
      Executive summary: getTypeSize -> getTypeStoreSize / getABITypeSize. · 44b8721d
      Duncan Sands authored
      The meaning of getTypeSize was not clear - clarifying it is important
      now that we have x86 long double and arbitrary precision integers.
      The issue with long double is that it requires 80 bits, and this is
      not a multiple of its alignment.  This gives a primitive type for
      which getTypeSize differed from getABITypeSize.  For arbitrary precision
      integers it is even worse: there is the minimum number of bits needed to
      hold the type (eg: 36 for an i36), the maximum number of bits that will
      be overwriten when storing the type (40 bits for i36) and the ABI size
      (i.e. the storage size rounded up to a multiple of the alignment; 64 bits
      for i36).
      
      This patch removes getTypeSize (not really - it is still there but
      deprecated to allow for a gradual transition).  Instead there is:
      
      (1) getTypeSizeInBits - a number of bits that suffices to hold all
      values of the type.  For a primitive type, this is the minimum number
      of bits.  For an i36 this is 36 bits.  For x86 long double it is 80.
      This corresponds to gcc's TYPE_PRECISION.
      
      (2) getTypeStoreSizeInBits - the maximum number of bits that is
      written when storing the type (or read when reading it).  For an
      i36 this is 40 bits, for an x86 long double it is 80 bits.  This
      is the size alias analysis is interested in (getTypeStoreSize
      returns the number of bytes).  There doesn't seem to be anything
      corresponding to this in gcc.
      
      (3) getABITypeSizeInBits - this is getTypeStoreSizeInBits rounded
      up to a multiple of the alignment.  For an i36 this is 64, for an
      x86 long double this is 96 or 128 depending on the OS.  This is the
      spacing between consecutive elements when you form an array out of
      this type (getABITypeSize returns the number of bytes).  This is
      TYPE_SIZE in gcc.
      
      Since successive elements in a SequentialType (arrays, pointers
      and vectors) need to be aligned, the spacing between them will be
      given by getABITypeSize.  This means that the size of an array
      is the length times the getABITypeSize.  It also means that GEP
      computations need to use getABITypeSize when computing offsets.
      Furthermore, if an alloca allocates several elements at once then
      these too need to be aligned, so the size of the alloca has to be
      the number of elements multiplied by getABITypeSize.  Logically
      speaking this doesn't have to be the case when allocating just
      one element, but it is simpler to also use getABITypeSize in this
      case.  So alloca's and mallocs should use getABITypeSize.  Finally,
      since gcc's only notion of size is that given by getABITypeSize, if
      you want to output assembler etc the same as gcc then getABITypeSize
      is the size you want.
      
      Since a store will overwrite no more than getTypeStoreSize bytes,
      and a read will read no more than that many bytes, this is the
      notion of size appropriate for alias analysis calculations.
      
      In this patch I have corrected all type size uses except some of
      those in ScalarReplAggregates, lib/Codegen, lib/Target (the hard
      cases).  I will get around to auditing these too at some point,
      but I could do with some help.
      
      Finally, I made one change which I think wise but others might
      consider pointless and suboptimal: in an unpacked struct the
      amount of space allocated for a field is now given by the ABI
      size rather than getTypeStoreSize.  I did this because every
      other place that reserves memory for a type (eg: alloca) now
      uses getABITypeSize, and I didn't want to make an exception
      for unpacked structs, i.e. I did it to make things more uniform.
      This only effects structs containing long doubles and arbitrary
      precision integers.  If someone wants to pack these types more
      tightly they can always use a packed struct.
      
      llvm-svn: 43620
      44b8721d
  18. Oct 26, 2007
  19. Oct 24, 2007
  20. Oct 18, 2007
  21. Oct 17, 2007
  22. Oct 03, 2007
  23. Sep 28, 2007
  24. Sep 14, 2007
  25. Sep 13, 2007
  26. Sep 06, 2007
    • Dale Johannesen's avatar
      Next round of APFloat changes. · bed9dc42
      Dale Johannesen authored
      Use APFloat in UpgradeParser and AsmParser.
      Change all references to ConstantFP to use the
      APFloat interface rather than double.  Remove
      the ConstantFP double interfaces.
      Use APFloat functions for constant folding arithmetic
      and comparisons.
      (There are still way too many places APFloat is
      just a wrapper around host float/double, but we're
      getting there.)
      
      llvm-svn: 41747
      bed9dc42
  27. Sep 04, 2007
    • David Greene's avatar
      · c656cbb8
      David Greene authored
      Update GEP constructors to use an iterator interface to fix
      GLIBCXX_DEBUG issues.
      
      llvm-svn: 41697
      c656cbb8
  28. Aug 27, 2007
  29. Aug 23, 2007
  30. Aug 21, 2007
  31. Aug 01, 2007
    • Dan Gohman's avatar
      More explicit keywords. · 34d442f2
      Dan Gohman authored
      llvm-svn: 40673
      34d442f2
    • David Greene's avatar
      · 17a5dfe6
      David Greene authored
      New CallInst interface to address GLIBCXX_DEBUG errors caused by
      indexing an empty std::vector.
      
      Updates to all clients.
      
      llvm-svn: 40660
      17a5dfe6
  32. Jul 27, 2007
Loading