Re: [Boost-build] [EXTERNAL] Major engine changes

Subject: Re: [Boost-build] [EXTERNAL] Major engine changes
From: Belcourt, K. Noel (kbelco_at_[hidden])
Date: 2011-12-03 14:15:12

On Dec 3, 2011, at 12:04 PM, Steven Watanabe wrote:

> On 12/03/2011 10:43 AM, Belcourt, K. Noel wrote:
>> On Nov 29, 2011, at 5:02 PM, Steven Watanabe wrote:
>>
>>> I've just committed a major rewrite of the
>>> jam interpreter. So, far, I'm seeing a 2x speed
>>> up running bjam -n -d0 in $BOOST_ROOT/status.
>>> I've tried to test my changes thoroughly, but, as
>>> always, there may be something that I missed.
>>> If anything breaks, please let me know, and I'll
>>> try to deal with it ASAP.
>>
>> It looks as if big endian (SunOS and AIX) bjam is segfaulting.  I
>> haven't had time yet to debug this but I noticed a few new warnings.
>>
>
> Is it okay with r75545? This introduced some endian-dependant
> code, but I thought I was careful.

I'll try this shortly.  One thing I noticed is that running the same  
bjam command fails most of the time, and works once in a while, though  
it seems to consistently fail in the nightly trunk on both platforms.   
Could be uninitialized memory.

>> "function.c", line 376: warning: implicit function declaration:
>> backtrace_line
>> "function.c", line 378: warning: implicit function declaration:  
>> backtrace
>> "function.c", line 2685: warning: implicit function declaration: glob
>> "jam.c", line 622: warning: implicit function declaration: pwd_done
>>
>
> Bother.  I think these are innocuous, though.

Yup.

-- Noel