Push the CURangeList down into the skeleton CU (where available) rather than the...
authorDavid Blaikie <dblaikie@gmail.com>
Mon, 3 Nov 2014 21:52:56 +0000 (21:52 +0000)
committerDavid Blaikie <dblaikie@gmail.com>
Mon, 3 Nov 2014 21:52:56 +0000 (21:52 +0000)
commit542616d47c5533a338e54db76dc99765410065ef
treef65407417c8164dd57d432666b5386df94af9b32
parentec0f3d755f6542bcff0125d10b9caae68155d3f7
Push the CURangeList down into the skeleton CU (where available) rather than the full CU

So that it may be shared between skeleton/full compile unit, for CU
ranges and other ranges to be added for fission+gmlt.

(at some point we might want some kind of object shared between the
skeleton and full compile units for all those things we only want one of
in that scope, rather than having the full unit always look through to
the skeleton... - alternatively, we might be able to have the skeleton
pointer (or another, separate pointer) point to the skeleton or to the
unit itself in non-fission, so we don't have to special case its
absence)

llvm-svn: 221186
llvm/lib/CodeGen/AsmPrinter/DwarfCompileUnit.cpp
llvm/lib/CodeGen/AsmPrinter/DwarfCompileUnit.h
llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp