Skip to content
  1. May 27, 2011
  2. May 24, 2011
  3. May 11, 2011
  4. May 10, 2011
  5. May 06, 2011
  6. May 05, 2011
  7. May 04, 2011
  8. May 03, 2011
  9. May 02, 2011
    • Devang Patel's avatar
      Emit debug info for global variables first. · 420ab5f1
      Devang Patel authored
      This works around a limitation in gdb which is reported by following inherit.exp test failures from gdb testsuite.
      
      gdb.cp/inherit.exp: print g_vB.vB::vb
      gdb.cp/inherit.exp: print g_vB.vB::vx
      gdb.cp/inherit.exp: print g_vC.vC::vc
      gdb.cp/inherit.exp: print g_vC.vC::vx
      gdb.cp/inherit.exp: print g_vD.vB::vb
      ...
      
      llvm-svn: 130702
      420ab5f1
  10. Apr 28, 2011
  11. Apr 26, 2011
  12. Apr 23, 2011
  13. Apr 22, 2011
  14. Apr 21, 2011
  15. Apr 18, 2011
  16. Apr 15, 2011
  17. Apr 13, 2011
  18. Apr 12, 2011
  19. Apr 09, 2011
  20. Apr 08, 2011
  21. Apr 06, 2011
  22. Apr 05, 2011
  23. Mar 26, 2011
  24. Mar 25, 2011
  25. Mar 24, 2011
  26. Mar 23, 2011
  27. Mar 22, 2011
    • Jakob Stoklund Olesen's avatar
      Reapply r128045 and r128051 with fixes. · ec0ac3ca
      Jakob Stoklund Olesen authored
      This will extend the ranges of debug info variables in registers until they are
      clobbered.
      
      Fix 1: Don't mistake DBG_VALUE instructions referring to incoming arguments on
      the stack with DBG_VALUE instructions referring to variables in the frame
      pointer. This fixes the gdb test-suite failure.
      
      Fix 2: Don't trace through copies to physical registers setting up call
      arguments. These registers are call clobbered, and the source register is more
      likely to be a callee-saved register that can be extended through the call
      instruction.
      
      llvm-svn: 128114
      ec0ac3ca
Loading