Skip to content
  1. Oct 16, 2010
  2. Oct 08, 2010
  3. Sep 04, 2010
  4. Aug 06, 2010
  5. Jul 22, 2010
  6. Jul 16, 2010
    • Dan Gohman's avatar
      Revert r108369, sorting llvm.dbg.declare information by source position, · 1e936277
      Dan Gohman authored
      since it doesn't work for front-ends which don't emit column information
      (which includes llvm-gcc in its present configuration), and doesn't
      work for clang for K&R style variables where the variables are declared
      in a different order from the parameter list.
      
      Instead, make a separate pass through the instructions to collect the
      llvm.dbg.declare instructions in order. This ensures that the debug
      information for variables is emitted in this order.
      
      llvm-svn: 108538
      1e936277
  7. Jul 15, 2010
  8. Apr 16, 2010
    • Bill Wendling's avatar
      The JIT calls TidyLandingPads to tidy up the landing pads. However, because the · 929f3c09
      Bill Wendling authored
      JIT doesn't use the MC back-end asm printer to emit labels that it uses, the
      section for the MCSymbol is never set. And thus the MCSymbol for the EH label
      isn't marked as "defined". Because of that, TidyLandingPads removes the needed
      landing pads from the JIT output. This breaks EH for every JIT program.
      
      This is a work-around for this limitation. We pass in the label locations
      map. If the label has a non-zero value, then it was "emitted" by the JIT and
      TidyLandingPads shouldn't remove that label.
      
      A nicer solution would be to mark the MCSymbol as "used" by the JIT and not rely
      upon the section being set to determine if it's defined or not.
      
      llvm-svn: 101453
      929f3c09
  9. Apr 15, 2010
  10. Apr 06, 2010
  11. Mar 23, 2010
  12. Mar 16, 2010
    • Chris Lattner's avatar
      Fix the third (and last known) case of code update problems due · db035a0a
      Chris Lattner authored
      to LLVM IR changes with addr label weirdness.  In the testcase, we
      generate references to the two bb's when codegen'ing the first
      function:
      
      _test1:                                 ## @test1
      	leaq	Ltmp0(%rip), %rax
      ..
      	leaq	Ltmp1(%rip), %rax
      
      Then continue to codegen the second function where the blocks
      get merged.  We're now smart enough to emit both labels, producing
      this code:
      
      _test_fun:                              ## @test_fun
      ## BB#0:                                ## %entry
      Ltmp1:                                  ## Block address taken
      Ltmp0:
      ## BB#1:                                ## %ret
      	movl	$-1, %eax
      	ret
      
      Rejoice.
      
      llvm-svn: 98595
      db035a0a
  13. Mar 15, 2010
  14. Mar 14, 2010
  15. Mar 13, 2010
    • Chris Lattner's avatar
      rearrange MCContext ownership. Before LLVMTargetMachine created it · e468f88b
      Chris Lattner authored
      and passing off ownership to AsmPrinter.  Now MachineModuleInfo
      creates it and owns it by value.  This allows us to use MCSymbols
      more consistently throughout the rest of the code generator, and
      simplifies a bit of code.  This also allows MachineFunction to 
      keep an MCContext reference handy, and cleans up the TargetRegistry
      interfaces for AsmPrinters.
      
      llvm-svn: 98450
      e468f88b
  16. Mar 09, 2010
  17. Feb 06, 2010
  18. Jan 28, 2010
  19. Jan 21, 2010
  20. Nov 24, 2009
  21. Nov 12, 2009
  22. Oct 08, 2009
  23. Sep 30, 2009
  24. Sep 16, 2009
  25. Aug 26, 2009
  26. Aug 23, 2009
  27. Aug 01, 2009
  28. Jul 20, 2009
Loading