Skip to content
  1. Feb 03, 2009
  2. Feb 02, 2009
  3. Jan 30, 2009
    • Devang Patel's avatar
      · c094970c
      Devang Patel authored
       Each input file is encoded as a separate compile unit in LLVM debugging
      information output. However, many target specific tool chains prefer to encode
      only one compile unit in an object file. In this situation, the LLVM code
      generator will include  debugging information entities in the compile unit 
      that is marked as main compile unit. The code generator accepts maximum one main
      compile unit per module. If a module does not contain any main compile unit 
      then the code generator will emit multiple compile units in the output object 
      file.
      
      [Part 1]
      
      Update DebugInfo APIs to accept optional boolean value while creating DICompileUnit  to mark the unit as "main" unit. By defaults all units are considered  non-main.  Update SourceLevelDebugging.html to document "main" compile unit.
      
      Update DebugInfo APIs to not accept and encode separate source file/directory entries while creating various llvm.dbg.* entities. There was a recent, yet to be documented, change to include this additional information so no documentation changes are required here.
      
      Update DwarfDebug to handle "main" compile unit. If "main" compile unit is seen then all DIEs are inserted into "main" compile unit. All other compile units are used to find source location for llvm.dbg.* values. If there is not any "main" compile unit then create unique compile unit DIEs for each llvm.dbg.compile_unit.
      
      [Part 2]
      
      Create separate llvm.dbg.compile_unit for each input file. Mark compile unit create for main_input_filename as "main" compile unit. Use appropriate compile unit, based on source location information collected from the tree node, while creating llvm.dbg.* values using DebugInfo APIs.
      
      ---
      
      This is Part 1.
      
      llvm-svn: 63400
      c094970c
    • Sanjiv Gupta's avatar
      Enable emitting of constant values in non-default address space as well. The... · 964a29f6
      Sanjiv Gupta authored
      Enable emitting of constant values in non-default address space as well. The APIs emitting constants now take an additional parameter signifying the address space in which to emit. The APIs like getData8BitsDirective() etc are made virtual enabling targets to be able to define appropirate directivers for various sizes and address spaces.
      
      llvm-svn: 63377
      964a29f6
    • Devang Patel's avatar
      Remove dead code, again. · 33a21670
      Devang Patel authored
      llvm-svn: 63358
      33a21670
    • Devang Patel's avatar
      Remove dead code. · 776a4c5b
      Devang Patel authored
      llvm-svn: 63357
      776a4c5b
    • Devang Patel's avatar
      Add DW_AT_declaration for class methods. · 4ba91058
      Devang Patel authored
      llvm-svn: 63356
      4ba91058
  4. Jan 28, 2009
  5. Jan 27, 2009
    • Devang Patel's avatar
      · 45c899cd
      Devang Patel authored
      Assorted debug info fixes.
      - DW_AT_bit_size is only suitable for bitfields.
      - Encode source location info for derived types.
      - Source location and type size info is not useful for subroutine_type (info is included in respective DISubprogram) and array_type.
      
      llvm-svn: 63077
      45c899cd
  6. Jan 26, 2009
  7. Jan 23, 2009
  8. Jan 22, 2009
  9. Jan 21, 2009
  10. Jan 20, 2009
  11. Jan 17, 2009
  12. Jan 16, 2009
Loading