<p dir="ltr">Got it, thanks! </p>
<br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 20, 2016, 2:26 AM Pavel Labath <<a href="mailto:labath@google.com">labath@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Our buildbot <<a href="http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake" rel="noreferrer" class="gmail_msg" target="_blank">http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake</a>><br class="gmail_msg">
runs the test suite with a selection of compilers, one of which is<br class="gmail_msg">
clang ToT (test3, test4). You should get an email from it if anything<br class="gmail_msg">
breaks.<br class="gmail_msg">
<br class="gmail_msg">
pl<br class="gmail_msg">
<br class="gmail_msg">
On 20 October 2016 at 00:24, Eric Christopher via lldb-dev<br class="gmail_msg">
<<a href="mailto:lldb-dev@lists.llvm.org" class="gmail_msg" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> On Wed, Oct 19, 2016 at 4:21 PM Tim Hammerquist <<a href="mailto:penryu@gmail.com" class="gmail_msg" target="_blank">penryu@gmail.com</a>> wrote:<br class="gmail_msg">
>><br class="gmail_msg">
>> On Wed, Oct 19, 2016 at 4:09 PM, Eric Christopher <<a href="mailto:echristo@gmail.com" class="gmail_msg" target="_blank">echristo@gmail.com</a>><br class="gmail_msg">
>> wrote:<br class="gmail_msg">
>>><br class="gmail_msg">
>>><br class="gmail_msg">
>>> On Wed, Oct 19, 2016 at 3:34 PM Tim Hammerquist <<a href="mailto:penryu@gmail.com" class="gmail_msg" target="_blank">penryu@gmail.com</a>> wrote:<br class="gmail_msg">
>>>><br class="gmail_msg">
>>>> I was mistaken.<br class="gmail_msg">
>>>><br class="gmail_msg">
>>>> The system toolchain builds stage1 llvm, clang & co.<br class="gmail_msg">
>>>> The system toolchain builds lldb containing the llvm/clang/etc bits.<br class="gmail_msg">
>>>> The system toolchain builds gtest test programs.<br class="gmail_msg">
>>>><br class="gmail_msg">
>>>> The stage1 compiler builds the python test inferiors.<br class="gmail_msg">
>>>><br class="gmail_msg">
>>><br class="gmail_msg">
>>> OK, then it sounds like at least some of the test programs are built with<br class="gmail_msg">
>>> the new compiler? IIRC the python test inferiors here are the programs that<br class="gmail_msg">
>>> are the meat of the testsuite for lldb yes?<br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>> Yes, these programs set up an expected state, and the python testsuite<br class="gmail_msg">
>> uses the lldb is used to debug these inferiors.<br class="gmail_msg">
>><br class="gmail_msg">
>> So it looks like we want two scenarios:<br class="gmail_msg">
>><br class="gmail_msg">
>> Scenario 1: build ToT lldb + llvm/clang/etc using Xcode toolchain; build<br class="gmail_msg">
>> test programs AND inferiors using Xcode toolchain<br class="gmail_msg">
>> Scenario 2: build ToT lldb + llvm/clang/etc using ToT compiler; build test<br class="gmail_msg">
>> programs AND inferiors using ToT compiler<br class="gmail_msg">
>><br class="gmail_msg">
>> Does that sound right?<br class="gmail_msg">
>><br class="gmail_msg">
>> S1 is _nearly_ what we have now; it would only require modifying the<br class="gmail_msg">
>> python test suite to build inferiors with the system compiler.<br class="gmail_msg">
>><br class="gmail_msg">
><br class="gmail_msg">
> I'd think so. It makes sure that current lldb is going to continue to work<br class="gmail_msg">
> with both new compilers as well as existing compilers and that current lldb<br class="gmail_msg">
> is buildable with both current compilers and newer compilers.<br class="gmail_msg">
><br class="gmail_msg">
> Thanks!<br class="gmail_msg">
><br class="gmail_msg">
> -eric<br class="gmail_msg">
><br class="gmail_msg">
>><br class="gmail_msg">
>> I can start looking at what's required to start S2. We've got some<br class="gmail_msg">
>> hardware coming to make it easier to bring up.<br class="gmail_msg">
>><br class="gmail_msg">
>> -Tim<br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>>> If so, then on check-in we should possibly see some difference on some<br class="gmail_msg">
>>> bot if they all use the same general configuration. I don't have a current<br class="gmail_msg">
>>> checkout so I don't know if the default -g is used or if it's set to a<br class="gmail_msg">
>>> different dwarf level. Currently it looks like clang will use dwarf4 by<br class="gmail_msg">
>>> default with -g:<br class="gmail_msg">
>>><br class="gmail_msg">
>>> echristo@dzur ~/tmp> ~/builds/build-llvm/bin/clang -c foo.c -o - -target<br class="gmail_msg">
>>> x86_64-apple-macosx10.11 -g | llvm-dwarfdump - | grep version | grep -v<br class="gmail_msg">
>>> clang<br class="gmail_msg">
>>> 0x00000000: Compile Unit: length = 0x00000037 version = 0x0004<br class="gmail_msg">
>>> abbr_offset = 0x0000 addr_size = 0x08 (next unit at 0x0000003b)<br class="gmail_msg">
>>> version: 2<br class="gmail_msg">
>>><br class="gmail_msg">
>>> where the first line is the debug_info header and the second is the<br class="gmail_msg">
>>> version in the line table.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Ted/Greg: Relatedly, what brought this up was the vliw aspect with<br class="gmail_msg">
>>> maximum_operations_per_instruction - it's being hard coded to 1 here and I'm<br class="gmail_msg">
>>> not sure how we want to deal with that on hexagon? Currently it'll be hard<br class="gmail_msg">
>>> set to 1 so line stepping will work as I imagine it currently does. That<br class="gmail_msg">
>>> said, if we wanted to take advantage of it then that's different. Primarily<br class="gmail_msg">
>>> I wasn't sure if Ted and folk had a debugger that did take advantage of it<br class="gmail_msg">
>>> if it was there.<br class="gmail_msg">
>>><br class="gmail_msg">
>>> Thanks!<br class="gmail_msg">
>>><br class="gmail_msg">
>>> -eric<br class="gmail_msg">
>>><br class="gmail_msg">
>>>><br class="gmail_msg">
>>>><br class="gmail_msg">
>>>> On Wed, Oct 19, 2016 at 3:28 PM, Eric Christopher <<a href="mailto:echristo@gmail.com" class="gmail_msg" target="_blank">echristo@gmail.com</a>><br class="gmail_msg">
>>>> wrote:<br class="gmail_msg">
>>>>><br class="gmail_msg">
>>>>><br class="gmail_msg">
>>>>><br class="gmail_msg">
>>>>> On Wed, Oct 19, 2016 at 3:26 PM Tim Hammerquist <<a href="mailto:penryu@gmail.com" class="gmail_msg" target="_blank">penryu@gmail.com</a>><br class="gmail_msg">
>>>>> wrote:<br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> The LLDB job in <a href="http://llvm.org" rel="noreferrer" class="gmail_msg" target="_blank">llvm.org</a> will build a stage1 RA with<br class="gmail_msg">
>>>>>> llvm+clang+libcxx+compiler-rt using the system compiler, and use the new<br class="gmail_msg">
>>>>>> compiler to build lldb.<br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> By default, this is kicked off automatically when a clang stage1 RA is<br class="gmail_msg">
>>>>>> successful, but can be manually triggered to build HEAD, or any revision<br class="gmail_msg">
>>>>>> desired.<br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> The python test suite (invoked with the xcodebuild target<br class="gmail_msg">
>>>>>> lldb-python-test-suite) uses the newly built compiler to build its test<br class="gmail_msg">
>>>>>> programs.<br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> <a href="http://lab.llvm.org:8080/green/job/lldb_build_test/21202/consoleFull#console-section-4" rel="noreferrer" class="gmail_msg" target="_blank">http://lab.llvm.org:8080/green/job/lldb_build_test/21202/consoleFull#console-section-4</a><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> However, the gtest suite (target lldb-gtest) uses the system (Xcode<br class="gmail_msg">
>>>>>> toolchain) compiler to build test programs.<br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> <a href="http://lab.llvm.org:8080/green/job/lldb_build_test/21202/artifact/lldb/test_output.zip" rel="noreferrer" class="gmail_msg" target="_blank">http://lab.llvm.org:8080/green/job/lldb_build_test/21202/artifact/lldb/test_output.zip</a><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>><br class="gmail_msg">
>>>>> This seems like something that should be fixed :)<br class="gmail_msg">
>>>>><br class="gmail_msg">
>>>>> -eric<br class="gmail_msg">
>>>>><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> -Tim<br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> On Wed, Oct 19, 2016 at 2:36 PM, Eric Christopher <<a href="mailto:echristo@gmail.com" class="gmail_msg" target="_blank">echristo@gmail.com</a>><br class="gmail_msg">
>>>>>> wrote:<br class="gmail_msg">
>>>>>>><br class="gmail_msg">
>>>>>>> From chatting with Tim it sounds like at least one lldb bot uses the<br class="gmail_msg">
>>>>>>> ToT compiler - we should probably verify that not only does it use that to<br class="gmail_msg">
>>>>>>> build lldb but uses it for the tests. That'll get us at least some testing<br class="gmail_msg">
>>>>>>> here.<br class="gmail_msg">
>>>>>>><br class="gmail_msg">
>>>>>>> -eric<br class="gmail_msg">
>>>>>>><br class="gmail_msg">
>>>>>>><br class="gmail_msg">
>>>>>>> On Wed, Oct 19, 2016 at 12:55 PM Greg Clayton via lldb-dev<br class="gmail_msg">
>>>>>>> <<a href="mailto:lldb-dev@lists.llvm.org" class="gmail_msg" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br class="gmail_msg">
>>>>>>>><br class="gmail_msg">
>>>>>>>> I believe we are good, but it would be good to verify via testing<br class="gmail_msg">
>>>>>>>> once a compiler becomes available.<br class="gmail_msg">
>>>>>>>><br class="gmail_msg">
>>>>>>>> Greg<br class="gmail_msg">
>>>>>>>><br class="gmail_msg">
>>>>>>>> > On Oct 19, 2016, at 12:19 PM, Ted Woodward via lldb-dev<br class="gmail_msg">
>>>>>>>> > <<a href="mailto:lldb-dev@lists.llvm.org" class="gmail_msg" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br class="gmail_msg">
>>>>>>>> ><br class="gmail_msg">
>>>>>>>> > This might affect us. Do we handle it correctly?<br class="gmail_msg">
>>>>>>>> ><br class="gmail_msg">
>>>>>>>> > <a href="https://reviews.llvm.org/D16697" rel="noreferrer" class="gmail_msg" target="_blank">https://reviews.llvm.org/D16697</a><br class="gmail_msg">
>>>>>>>> ><br class="gmail_msg">
>>>>>>>> > --<br class="gmail_msg">
>>>>>>>> > Qualcomm Innovation Center, Inc.<br class="gmail_msg">
>>>>>>>> > The Qualcomm Innovation Center, Inc. is a member of Code Aurora<br class="gmail_msg">
>>>>>>>> > Forum, a Linux Foundation Collaborative Project<br class="gmail_msg">
>>>>>>>> ><br class="gmail_msg">
>>>>>>>> > _______________________________________________<br class="gmail_msg">
>>>>>>>> > lldb-dev mailing list<br class="gmail_msg">
>>>>>>>> > <a href="mailto:lldb-dev@lists.llvm.org" class="gmail_msg" target="_blank">lldb-dev@lists.llvm.org</a><br class="gmail_msg">
>>>>>>>> > <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br class="gmail_msg">
>>>>>>>><br class="gmail_msg">
>>>>>>>> _______________________________________________<br class="gmail_msg">
>>>>>>>> lldb-dev mailing list<br class="gmail_msg">
>>>>>>>> <a href="mailto:lldb-dev@lists.llvm.org" class="gmail_msg" target="_blank">lldb-dev@lists.llvm.org</a><br class="gmail_msg">
>>>>>>>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>><br class="gmail_msg">
>>>>>> --<br class="gmail_msg">
>>>>>> Tim <<a href="mailto:penryu@gmail.com" class="gmail_msg" target="_blank">penryu@gmail.com</a>><br class="gmail_msg">
>>>><br class="gmail_msg">
>>>><br class="gmail_msg">
>>>><br class="gmail_msg">
>>>><br class="gmail_msg">
>>>> --<br class="gmail_msg">
>>>> Tim <<a href="mailto:penryu@gmail.com" class="gmail_msg" target="_blank">penryu@gmail.com</a>><br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>> --<br class="gmail_msg">
>> Tim <<a href="mailto:penryu@gmail.com" class="gmail_msg" target="_blank">penryu@gmail.com</a>><br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> _______________________________________________<br class="gmail_msg">
> lldb-dev mailing list<br class="gmail_msg">
> <a href="mailto:lldb-dev@lists.llvm.org" class="gmail_msg" target="_blank">lldb-dev@lists.llvm.org</a><br class="gmail_msg">
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br class="gmail_msg">
><br class="gmail_msg">
</blockquote></div>