[llvm] r214761 - Reapply "DebugInfo: Ensure that all debug location scope chains from instructions within a function, lead to the function itself."

David Blaikie dblaikie at gmail.com
Tue Aug 5 09:57:01 PDT 2014


Thanks for the reproduction (preprocessed really helped since I don't
build on a mac). I've reverted in r214880 while I reduce and
investigate the issue.

On Tue, Aug 5, 2014 at 7:29 AM, Tim Northover <t.p.northover at gmail.com> wrote:
> Hi David,
>
> On 4 August 2014 20:30, David Blaikie <dblaikie at gmail.com> wrote:
>> Author: dblaikie
>> Date: Mon Aug  4 14:30:08 2014
>> New Revision: 214761
>>
>> URL: http://llvm.org/viewvc/llvm-project?rev=214761&view=rev
>> Log:
>> Reapply "DebugInfo: Ensure that all debug location scope chains from instructions within a function, lead to the function itself."
>
> I'm afraid this one seems to be causing some problems with
> self-hosting on Darwin.
>
>>      // FIXME: There shouldn't be any variables without DIEs.
>> -    if (!VariableDie)
>> -      continue;
>> +    assert(VariableDie);
>
> This assertion is triggering for me.
>
> A Clang command causing the assert (from a CMake build dir with libc++
> symlinked into include) is:
>
> $ bin/clang -g -D __STDC_CONSTANT_MACROS -D __STDC_FORMAT_MACROS -D
> __STDC_LIMIT_MACROS -stdlib=libc++ -O2 -std=c++11
> -fvisibility-inlines-hidden  -fno-rtti -x c++
> ../llvm/lib/Analysis/AliasSetTracker.cpp -I include/ -I include/clang/
> -I ../llvm/include/
>
> If that doesn't work for you, I've attached the preprocessed output,
> which also triggers it (even on Linux) with:
> $ bin/clang++ -target x86_64-apple-macosx10.9 -std=c++11 Analysis.cpp -g -O2 -c
>
> Could you take a look?
>
> Cheers.
>
> Tim.



More information about the llvm-commits mailing list