Skip to content
  1. Jun 25, 2010
  2. Apr 20, 2010
  3. Apr 17, 2010
  4. Apr 16, 2010
  5. Apr 15, 2010
  6. Oct 25, 2009
  7. Oct 06, 2009
  8. Sep 19, 2009
  9. Aug 14, 2009
  10. Aug 13, 2009
  11. Aug 06, 2009
  12. Jul 31, 2009
  13. Jul 30, 2009
  14. Jul 29, 2009
  15. Jul 28, 2009
  16. Jul 25, 2009
  17. Jul 22, 2009
  18. Jul 15, 2009
  19. Jul 13, 2009
    • Owen Anderson's avatar
      Begin the painful process of tearing apart the rat'ss nest that is... · 53a52215
      Owen Anderson authored
      Begin the painful process of tearing apart the rat'ss nest that is Constants.cpp and ConstantFold.cpp.
      This involves temporarily hard wiring some parts to use the global context.  This isn't ideal, but it's
      the only way I could figure out to make this process vaguely incremental.
      
      llvm-svn: 75445
      53a52215
  20. Jul 08, 2009
  21. Mar 07, 2009
    • Duncan Sands's avatar
      Introduce new linkage types linkonce_odr, weak_odr, common_odr · 12da8ce3
      Duncan Sands authored
      and extern_weak_odr.  These are the same as the non-odr versions,
      except that they indicate that the global will only be overridden
      by an *equivalent* global.  In C, a function with weak linkage can
      be overridden by a function which behaves completely differently.
      This means that IP passes have to skip weak functions, since any
      deductions made from the function definition might be wrong, since
      the definition could be replaced by something completely different
      at link time.   This is not allowed in C++, thanks to the ODR
      (One-Definition-Rule): if a function is replaced by another at
      link-time, then the new function must be the same as the original
      function.  If a language knows that a function or other global can
      only be overridden by an equivalent global, it can give it the
      weak_odr linkage type, and the optimizers will understand that it
      is alright to make deductions based on the function body.  The
      code generators on the other hand map weak and weak_odr linkage
      to the same thing.
      
      llvm-svn: 66339
      12da8ce3
  22. Jan 16, 2009
  23. 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
  24. Aug 17, 2008
    • Gordon Henriksen's avatar
      Rename some GC classes so that their roll will hopefully be clearer. · d930f913
      Gordon Henriksen authored
      In particular, Collector was confusing to implementors. Several
      thought that this compile-time class was the place to implement
      their runtime GC heap. Of course, it doesn't even exist at runtime.
      Specifically, the renames are:
      
        Collector               -> GCStrategy
        CollectorMetadata       -> GCFunctionInfo
        CollectorModuleMetadata -> GCModuleInfo
        CollectorRegistry       -> GCRegistry
        Function::getCollector  -> getGC (setGC, hasGC, clearGC)
      
      Several accessors and nested types have also been renamed to be
      consistent. These changes should be obvious.
      
      llvm-svn: 54899
      d930f913
    • Gordon Henriksen's avatar
      Factor GC metadata table assembly generation out of Collector in preparation... · bcef14d2
      Gordon Henriksen authored
      Factor GC metadata table assembly generation out of Collector in preparation for splitting AsmPrinter into its own library.
      
      llvm-svn: 54881
      bcef14d2
  25. Aug 08, 2008
  26. May 13, 2008
  27. May 08, 2008
  28. May 07, 2008
  29. Apr 13, 2008
  30. Apr 06, 2008
  31. Jan 24, 2008
Loading