Skip to content
  1. Apr 07, 2011
  2. Apr 04, 2011
  3. Apr 02, 2011
  4. Mar 30, 2011
  5. Mar 24, 2011
  6. Mar 23, 2011
  7. Mar 22, 2011
  8. Mar 11, 2011
  9. Mar 09, 2011
    • John McCall's avatar
      Use the "undergoes default argument promotion" bit on parameters to · a738c25f
      John McCall authored
      simplify the logic of initializing function parameters so that we don't need
      both a variable declaration and a type in FunctionArgList.  This also means
      that we need to propagate the CGFunctionInfo down in a lot of places rather
      than recalculating it from the FAL.  There's more we can do to eliminate
      redundancy here, and I've left FIXMEs behind to do it.
      
      llvm-svn: 127314
      a738c25f
  10. Feb 28, 2011
  11. Feb 22, 2011
  12. Feb 20, 2011
  13. Feb 08, 2011
  14. Feb 03, 2011
  15. Feb 02, 2011
  16. Jan 29, 2011
  17. Jan 08, 2011
  18. Dec 04, 2010
  19. Nov 13, 2010
  20. Nov 01, 2010
  21. Oct 26, 2010
  22. Oct 15, 2010
  23. Sep 17, 2010
    • John McCall's avatar
      Currently we're initializing the vtable pointers of a class only after · 769250ea
      John McCall authored
      the bases are completely initialized.  This won't work --- base
      initializer expressions can rely on the vtables having been set up.
      Check for uses of 'this' in the initializers and force a vtable
      initialization if found.
      
      This might not be good enough;  we might need to extend this to handle
      the possibility of arbitrary code finding an external reference to this
      (not yet completely-constructed!) object and accessing through it,
      in which case we'll probably find ourselves doing a lot more unnecessary
      stores.
      
      llvm-svn: 114153
      769250ea
  24. Sep 15, 2010
    • John McCall's avatar
      one piece of code is responsible for the lifetime of every aggregate · 7a626f63
      John McCall authored
      slot.  The easiest way to do that was to bundle up the information
      we care about for aggregate slots into a new structure which demands
      that its creators at least consider the question.
      
      I could probably be convinced that the ObjC 'needs GC' bit should
      be rolled into this structure.
      Implement generalized copy elision.  The main obstacle here is that
      IR-generation must be much more careful about making sure that exactly
      
      llvm-svn: 113962
      7a626f63
  25. Aug 21, 2010
  26. Aug 11, 2010
  27. Aug 07, 2010
    • John McCall's avatar
      Store inheritance paths after CastExprs instead of inside them. · cf142165
      John McCall authored
      This takes some trickery since CastExpr has subclasses (and indeed,
      is abstract).
      
      Also, smoosh the CastKind into the bitfield from Expr.
      
      Drops two words of storage from Expr in the common case of expressions
      which don't need inheritance paths.  Avoids a separate allocation and
      another word of overhead in cases needing inheritance paths.  Also has
      the advantage of not leaking memory, since destructors for AST nodes are
      never run.
      
      llvm-svn: 110507
      cf142165
  28. Jul 21, 2010
  29. Jul 13, 2010
    • John McCall's avatar
      Teach IR generation how to lazily emit cleanups. This has a lot of advantages, · 2b7fc382
      John McCall authored
      mostly in avoiding unnecessary work at compile time but also in producing more
      sensible block orderings.
      
      Move the destructor cleanups for local variables over to use lazy cleanups.
      Eventually all cleanups will do this;  for now we have some awkward code
      duplication.
      
      Tell IR generation just to never produce landing pads in -fno-exceptions.
      This is a much more comprehensive solution to a problem which previously was
      half-solved by checks in most cleanup-generation spots.
      
      llvm-svn: 108270
      2b7fc382
  30. Jul 07, 2010
  31. Jul 06, 2010
    • John McCall's avatar
      Validated by nightly-test runs on x86 and x86-64 darwin, including after · bd30929e
      John McCall authored
      self-host.  Hopefully these results hold up on different platforms.  
      
      I tried to keep the GNU ObjC runtime happy, but it's hard for me to test.
      Reimplement how clang generates IR for exceptions.  Instead of creating new
      invoke destinations which sequentially chain to the previous destination,
      push a more semantic representation of *why* we need the cleanup/catch/filter
      behavior, then collect that information into a single landing pad upon request.
      
      Also reorganizes how normal cleanups (i.e. cleanups triggered by non-exceptional
      control flow) are generated, since it's actually fairly closely tied in with
      the former.  Remove the need to track which cleanup scope a block is associated
      with.
      
      Document a lot of previously poorly-understood (by me, at least) behavior.
      
      The new framework implements the Horrible Hack (tm), which requires every
      landing pad to have a catch-all so that inlining will work.  Clang no longer
      requires the Horrible Hack just to make exceptions flow correctly within
      a function, however.  The HH is an unfortunate requirement of LLVM's EH IR.
      
      llvm-svn: 107631
      bd30929e
Loading