Re: [boost] [Boost-users] [release] Boost 1.62.0 Release Candidate 1

Subject: Re: [boost] [Boost-users] [release] Boost 1.62.0 Release Candidate 1
From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2016-09-28 00:52:53

On Tue, Sep 27, 2016 at 7:14 PM, Edward Diener <eldiener_at_[hidden]>
wrote:

> On 9/27/2016 9:24 PM, Marshall Clow wrote:
>
>>
>>
>> On Mon, Sep 26, 2016 at 5:52 PM, Marshall Clow <mclow.lists_at_[hidden]
>> <mailto:mclow.lists_at_[hidden]>> wrote:
>>
>>     On Mon, Sep 26, 2016 at 7:36 AM, Rene Rivera <grafikrobot_at_[hidden]
>>     <mailto:grafikrobot_at_[hidden]>> wrote:
>>
>>         The release candidates for the 1.62.0 release are now available
>> at:
>>
>>
>>     [snip]
>>
>>
>>
>>     Now to run some tests....
>>
>>     -- Marshall
>>
>>
>> The test "vmd/test/test_doc_modifiers_return_type.cpp" hangs clang.
>> Reported as https://llvm.org/bugs/show_bug.cgi?id=30546
>>
>
> Evidently clang runs out of memory. Note that with VC++ and gcc the test
> passes.
>
> I don't know why clang would run out ot memory while VC++ and gcc do not
> but I have not queried the clang mailing list further about it. An educated
> guess is that clang calculates some fixed size for the preprocessor and
> when macro expansions cause that fixed size to overrun you get an out of
> memory condition. I can hardly believe that the preprocessor is really
> running out of virtual memory, no matter how complicated the preprocessor
> code gets in VMD.
>
>
When I was discussing the problem with Richard, he opined that that might
be a problem, if the preprocessed source exceeded 1 GB in size - which it
doesn't.  (GCC expands this test to about 700K)

So I suspect it is "just a bug"

-- Marshall