diff options
| author | David Blaikie <dblaikie@gmail.com> | 2013-06-16 20:34:15 +0000 |
|---|---|---|
| committer | David Blaikie <dblaikie@gmail.com> | 2013-06-16 20:34:15 +0000 |
| commit | 0252265be09bcd94c72cea95e21a773b3ea1c638 (patch) | |
| tree | 8a36a32a3f4d9d42ada095959fcf6cdc2ebc598d /llvm/lib/Target/Sparc | |
| parent | 80d055494973e23dda00914c8f214e289831a341 (diff) | |
| download | bcm5719-llvm-0252265be09bcd94c72cea95e21a773b3ea1c638.tar.gz bcm5719-llvm-0252265be09bcd94c72cea95e21a773b3ea1c638.zip | |
Debug Info: Simplify Frame Index handling in DBG_VALUE Machine Instructions
Rather than using the full power of target-specific addressing modes in
DBG_VALUEs with Frame Indicies, simply use Frame Index + Offset. This
reduces the complexity of debug info handling down to two
representations of values (reg+offset and frame index+offset) rather
than three or four.
Ideally we could ensure that frame indicies had been eliminated by the
time we reached an assembly or dwarf generation, but I haven't spent the
time to figure out where the FIs are leaking through into that & whether
there's a good place to convert them. Some FI+offset=>reg+offset
conversion is done (see PrologEpilogInserter, for example) which is
necessary for some SelectionDAG assumptions about registers, I believe,
but it might be possible to make this a more thorough conversion &
ensure there are no remaining FIs no matter how instruction selection
is performed.
llvm-svn: 184066
Diffstat (limited to 'llvm/lib/Target/Sparc')
0 files changed, 0 insertions, 0 deletions
