On 4 May 2017 at 12:52, Alex L wrote:
>
>
> On 4 May 2017 at 12:43, Alex L wrote:
>
>>
>>
>> On 3 May 2017 at 22:23, Richard Smith wrote:
>>
>>> On 3 May 2017 at 07:29, Alex L wrote:
>>>
Hi Richard,
This commit has caused an infinite loop in one of our internal libclang
bas
On 4 May 2017 at 12:43, Alex L wrote:
>
>
> On 3 May 2017 at 22:23, Richard Smith wrote:
>
>> On 3 May 2017 at 07:29, Alex L wrote:
>>
>>> Hi Richard,
>>>
>>> This commit has caused an infinite loop in one of our internal libclang
>>> based tooling tests. It keeps repeating the following frames
On 3 May 2017 at 22:23, Richard Smith wrote:
> On 3 May 2017 at 07:29, Alex L wrote:
>
>> Hi Richard,
>>
>> This commit has caused an infinite loop in one of our internal libclang
>> based tooling tests. It keeps repeating the following frames:
>>
>> frame #33528: 0x000109db2edf libclang
On 3 May 2017 at 07:29, Alex L wrote:
> Hi Richard,
>
> This commit has caused an infinite loop in one of our internal libclang
> based tooling tests. It keeps repeating the following frames:
>
> frame #33528: 0x000109db2edf libclang.dylib`clang::
> DiagnosticsEngine::ReportDelayed(this=0
Hi Richard,
This commit has caused an infinite loop in one of our internal libclang
based tooling tests. It keeps repeating the following frames:
frame #33528: 0x000109db2edf
libclang.dylib`clang::DiagnosticsEngine::ReportDelayed(this=0x00011c002c00)
at Diagnostic.cpp:149
frame #3
Author: rsmith
Date: Tue May 2 19:28:49 2017
New Revision: 301992
URL: http://llvm.org/viewvc/llvm-project?rev=301992&view=rev
Log:
[modules] Round-trip -Werror flag through explicit module build.
The intent for an explicit module build is that the diagnostics produced within
the module are thos
