This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[David Abrahams] PCH and GCC ICEing on boost/python.cpp


This was a courtesy copy Dave Abrahams sent me.  

forwarding it here for future reference.


--- Begin Message ---
The following message is a courtesy copy of an article
that has been posted to gmane.comp.python.c++ as well.

Jonathan Brandmeyer <jbrandmeyer@earthlink.net> writes:

> On Fri, 2003-10-10 at 18:46, Niall Douglas wrote:
>> The PCH file must be the FIRST include and the ONLY precompiled 
>> header for v3.4 of GCC at least (I'm guessing they'll improve this 
>> with time). For MSVC you can have as many headers as you like before 
>> the #pragma hdrstop. It should be the user's responsibility to ensure 
>> common.h includes <boost/python.hpp> and anything else.
>> 
>> The above gives the maximum flexibility to users AFAICS. Comments 
>> from the group?
>> 
>> Cheers,
>> Niall
>
> I tried out a CVS version of GCC a few days ago to try out the PCH
> support in the next compiler.  It ICEed with a segmentation fault when
> trying to compile a header file that only included boost/python.hpp. 
> Given that failure, my only comment is that it will be hard to
> operationally test Pyste's support for PCH with GCC.

Did you report the bug to the GCC maintainers?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

--- End Message ---

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]