Boost C++ Libraries: Ticket #2180: Errors on binary serialization of vector

owner changed

Robert Ramey — Mon, 11 Aug 2008 21:28:01 GMT

owner changed from Robert Ramey to Matthias Troyer

Mathias,

Could you take a look at this for me please?

Robert Ramey

anonymous — Mon, 11 Aug 2008 21:45:11 GMT

I will have to install gcc 4.1 It works for me using gcc 4.0 and gcc 4.2

k_karanikolas@… — Tue, 12 Aug 2008 17:48:48 GMT

I investigated a little bit further which version triggers the error, and it appears to be 4.1.0.

I compiled a stock gcc-4.1.0, and the error is still there.

Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../configure --prefix=/home/kostas/local/ --enable-languages=c,c++
Thread model: posix
gcc version 4.1.0

Ubuntu's gcc-4.1.3 however, does not trigger this error

Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.1.3 20080308 (prerelease) (Ubuntu 4.1.2-21ubuntu1)

Unfortunately, I am using 4.1.0 not by choice, but because the community supported compiler/toolset for my target platform (PSP) is based on stock gcc-4.1.0 plus some back-end patches. I'll try to apply the patches to the latest of the 4.1 line and see if the problem is still there. At any rate I think this issue can potentially "bite" someone using 4.1.0.

Also in the mailing list archives, (http://lists.boost.org/boost-users/2008/07/38112.php) I've found something that resembles the errors I'm getting. So it maybe possible to construct a workaround to what appears to be a compiler bug.

Thanks again,

Kostas

k_karanikolas@… — Mon, 18 Aug 2008 07:59:20 GMT

One more update. I was able to update my toolchain to 4.1.2 and the previously mentioned errors have gone. It appears that there is some kind of compiler bug in gcc in version 4.1.0. At any rate you may want to close this issue, but perhaps add some kind of warning in the documentation, to help people that may encounter similar problems.

Thanks Kostas

Matthias Troyer — Mon, 18 Aug 2008 17:45:46 GMT

We can turn array optimizations off for 4.1.0. That way it will still compile, however at the cost of substantially decreased performance. Would you prefer that over compiler errors due to compiler bugs?

k_karanikolas@… — Thu, 21 Aug 2008 08:00:30 GMT

I think it might be better to opt for compatibility rather than performance. Perhaps even controlling the inclusion of these optimizations through a #define. This way it may make it easier for people to diagnose such a problems which may exist in other compiler versions.

Matthias Troyer — Mon, 03 Aug 2009 20:55:14 GMT

The offending code has been rewritten some time ago. Can someone with access to the involved compilers please try if this is still an issue?

status changed; resolution set

anonymous — Wed, 05 Aug 2009 16:01:16 GMT

status new → closed
resolution → fixed

I'm closing this since I believe that this issue should not occur with the current code.