Re: [Boost-bugs] [Boost C++ Libraries] #977: bjam crashes when compiled with gcc 4.2

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #977: bjam crashes when compiled with gcc 4.2
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2007-07-24 18:55:30

#977: bjam crashes when compiled with gcc 4.2
-----------------------------------+----------------------------------------
  Reporter:  ismail_at_[hidden]  |       Owner:  grafik     
      Type:  Bugs                  |      Status:  assigned   
 Milestone:                        |   Component:  bjam       
   Version:  Boost.Jam 3.1.14      |    Severity:  Showstopper
Resolution:                        |    Keywords:             
-----------------------------------+----------------------------------------
Comment (by bk_at_[hidden]):

 Hm, this bug seems to be quite odd to reproduce. It reproduces here with
 this gcc:

 Configured with: ../configure --enable-threads=posix --prefix=/usr --with-
 local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man
 --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-
 languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release
 --with-gxx-include-dir=/usr/include/c++/4.2.1 --enable-ssp --disable-
 libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-
 shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-
 libstdcxx-pch --program-suffix=-4.2 --enable-version-specific-runtime-libs
 --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux
 Thread model: posix
 gcc version 4.2.1 20070705 (prerelease) (SUSE Linux)

 Other architectures with equivalent gcc also fail: i386 ia64, ppc, ppc64,
 s390, s390x
 (no platform to which we have works)

 Now the odd thing: It seems it worked with the same gcc version before,
 same sources, just in the previous rebuild of all openSUSE packages (I
 still try to verify this, as the boost-jam tarball has no testsuite, the
 segfault was not detected directly, only when trying to builld boost
 itself)

 The main change in gcc42 before that was an update from
 suse-gcc-4_2-branch head (r126079) to
 suse-gcc-4_2-branch head (r126359)

 glibc was changes to the lastest glibc-2.6 head, shortly before.

 Anyway, we are applying the change regarding-fno-strict-aliasing in our
 builds.

 If I'd have a vote, as that should not be a major performance isssue for
 jam, I'd just
 apply the workaround if you are not going to look for the real fix.
 Pity that you need yor own jam!

-- 
Ticket URL: <http://svn.boost.org/trac/boost/ticket/977#comment:9>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.