[PATCH] D44384: [DEBUGINFO] Add -no-dwarf-debug-ranges option.

David Blaikie via llvm-commits llvm-commits at lists.llvm.org
Mon Mar 12 11:26:12 PDT 2018


If you could simplify the test down to the smallest example that produces
ranges, that'd be good - which should be achievable with two functions in
distinct sections ('a' and 'b' for example).

On Mon, Mar 12, 2018 at 11:11 AM Alexey Bataev via Phabricator <
reviews at reviews.llvm.org> wrote:

> ABataev added inline comments.
>
>
> ================
> Comment at: test/DebugInfo/X86/no_debug_ranges.ll:10-44
> +; Function Attrs: noinline nounwind optnone uwtable
> +define void @_Z2f1v() #0 section "a" !dbg !7 {
> +entry:
> +  ret void, !dbg !10
> +}
> +
> +; Function Attrs: noinline nounwind optnone uwtable
> ----------------
> dblaikie wrote:
> > What's interesting about these 4 sections/6 functions, more than having
> two sections/functions? (trying to understand what nuances are being tested
> here - perhaps a comment in the test case would be helpful to explain the
> motivation)
> Nothing special, I just copied an existing test that definitely produces
> ranges by default. Test just checks that with the flag
> `-no-dwarf-ranges-section` no .debug_ranges section is emitted. But I agree
> that it would be good to test how the addresses are emitted
>
>
> Repository:
>   rL LLVM
>
> https://reviews.llvm.org/D44384
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20180312/aa2cba1c/attachment.html>


More information about the llvm-commits mailing list