#1491 closed Bugs (fixed)
value_initialized leaves data uninitialized, when using GCC
| Reported by: | niels_dekker | Owned by: | niels_dekker |
|---|---|---|---|
| Milestone: | Boost 1.35.0 | Component: | None |
| Version: | Boost 1.34.1 | Severity: | Problem |
| Keywords: | Cc: |
Description
The data of an instance of boost::value_initialized<T> may not be initialized properly, when using GCC. Therefore some tests recently added to trunk/libs/utility/value_init_test.cpp are expected to fail on GCC test platforms. This is caused by some GCC compiler issues:
GCC Bugzilla Bug 30111 Value-initialization of POD base class doesn't initialize members, reported by Jonathan Wakely
GCC Bugzilla Bug 33916 Default constructor fails to initialize array members, reported by Michael Elizabeth Chastain
Fernando Cacciola and I have already discussed this issue. I hope to have a workaround within a few weeks... Hopefully this workaround will be the same for GCC, Borland and MSVC. See also Ticket #1459 and #1217.
Change History (3)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The workaround is merged from the trunk to the release branch, changeset [42501], so the issue should be resolved with the next release of Boost, version 1.35.0.
comment:3 by , 15 years ago
| Milestone: | To Be Determined → Boost 1.35.0 |
|---|
A workaround is provided at the trunk, with changeset [41942]. See also the Boost developer mailing list, Re: [utility] value_init workaround fixed [Re: value_init_test failure].