On targets where f32 is not legal, we have to look through a BITCAST SDNode to find the register that an argument is stored in when emitting debug info, or we will not be able to emit a DW_AT_location for it.
Details
Diff Detail
Event Timeline
Looks plausible, but I haven't done much with the debug info location side of things - wouldn't mind a second opinion.
test/DebugInfo/ARM/float-args.ll | ||
---|---|---|
4 | Usually I run the llc and dwarfdump commands together, rather than using a temp file: llc -o - | llvm-dwarfdump - | FileCheck (plus all the other usual args) | |
10 | Do you need a use of 'p' for this test case, or just the argument 'p'? (do you need the arithmetic - or can you just "return p" (or sometimes I'll use a stub-function to ensure a use: void f1(float); void f2(float p) { f1(p); } to make it clear that a use is necessary (& the call can't be optimized away) but it doesn't really matter what that use is)) |
Usually I run the llc and dwarfdump commands together, rather than using a temp file:
(plus all the other usual args)