Skip to content
  1. Oct 24, 2012
  2. Oct 23, 2012
  3. Oct 20, 2012
  4. Oct 19, 2012
  5. Oct 18, 2012
  6. Oct 17, 2012
    • Eric Christopher's avatar
      Revert r158009 since there are some uses of artificial functions in · 086da341
      Eric Christopher authored
      debug info.
      
      llvm-svn: 166109
      086da341
    • John McCall's avatar
      Set a special flag in class metadata when an Objective-C class · 0d54a17b
      John McCall authored
      has ivars that require destruction, but none that require anything
      except zero-initialization.  This is common in ARC and (when true
      throughout a class hierarchy) permits the elimination of an
      unnecessary message-send during allocation.
      
      llvm-svn: 166088
      0d54a17b
    • John McCall's avatar
      Organize and rename the magic constants for class flags. · ef19dbb6
      John McCall authored
      No functionality change.
      
      llvm-svn: 166087
      ef19dbb6
    • John McCall's avatar
      At -O0, prefer objc_storeStrong with a null new value to the · e68b8f4d
      John McCall authored
      combination of a load+objc_release;  this is generally better
      for tools that try to track why values are retained and
      released.  Also use objc_storeStrong when copying a block
      (again, only at -O0), which requires us to do a preliminary
      store of null in order to compensate for objc_storeStrong's
      assign semantics.
      
      llvm-svn: 166085
      e68b8f4d
    • Nico Weber's avatar
      "'Might as well make it static const.' -- John McCall" -- Michael Scott · 9272407c
      Nico Weber authored
      llvm-svn: 166080
      9272407c
    • David Blaikie's avatar
      PR13684: Emit vtable entries for deleted functions as __cxa_deleted_function. · eb7d598c
      David Blaikie authored
      This is consistent/interoperable with GCC 4.7 (& __cxa_deleted_function isn't
      present in 4.4 - not sure when it got added, but you'll need something with
      that function available for this to work).
      
      llvm-svn: 166069
      eb7d598c
    • Derek Schuff's avatar
      Add pnaclcall convention to Native Client targets. · a202096d
      Derek Schuff authored
      Because PNaCl bitcode must be target-independent, it uses some
      different bitcode representations from other targets (e.g. byval and
      sret for structures). This means that without additional type
      information, it cannot meet some native ABI requirements for some
      targets (e.g. passing structures containing unions by value on
      x86-64). To allow generation of code which uses the correct native
      ABIs, we also support triples such as x86_64-nacl, which uses
      target-dependent IR (as opposed to le32-nacl, which uses byval and
      sret).
      
      To allow interoperation between the two types of code, this patch adds
      a calling convention attribute to be used in code compiled with the
      target-dependent triple, which will generate code using the le32-style
      bitcode. This calling convention does not need to be explicitly
      supported in the backend because it determines bitcode representation
      rather than native conventions (the backend just needs to undersand
      how to handle byval and sret for the Native Client OS).
      
      This patch implements __attribute__((pnaclcall)) to generate calls in
      bitcode according to the le32 bitcode conventions, an attribute which
      is accepted by any Native Client target, but issues a warning
      otherwise.
      
      llvm-svn: 166065
      a202096d
  7. Oct 16, 2012
  8. Oct 15, 2012
  9. Oct 14, 2012
  10. Oct 13, 2012
Loading