[cfe-dev] Clang vs. Boost release branch
dgregor at apple.com
Wed Oct 12 18:13:03 PDT 2011
On Oct 11, 2011, at 7:31 AM, Douglas Gregor wrote:
> Hi All,
> Want to help the Clang C++ effort? Here's a great way to get started…
> Clang is about to branch for the 3.0 release, and Boost is putting the finishing touches on its 1.48.0 release, so now would be a great time to make sure that the two upcoming releases work wonderfully together. Unfortunately, there are a number of problems that make the experience less than satisfying.
> I went ahead and ran Boost's release-branch regression tests with Clang trunk on Mac OS X 10.7. The results are posted here in the dgregor2/clang-darwin-3.0 column:
> I've provided a rough categorization of failures below, some of which are Clang bugs and others that are Boost bugs. If you want to help, please look into some failures to understand where the problem lies:
> - If it's a Clang bug, please go ahead and file a bug at http://llvm.org/bugs/ with a reduced (= does not involve Boost directly) bug.
> - If it's a Boost bug, please report it to Boost and (if possible) provide a patch
> - If it's a platform bug, please report it to Boost and we can mark it up as an "expected failure"
> When time permits, I'll also try to run Boost's tests in C++0x mode and with libc++. Help wanted here as well :)
> Regression test failures, by library:
> Container: 4 __has_nothrow_assign failures due to access control private members
> Interprocess: 4 __has_nothrow_assign failures
> 3 compiler crashes (doc_unique_ptr, shared_ptr_test, unique_ptr_test)
> Move: 5 __has_nothrow_assign failures
> Variant: 1 __has_nothrow_assign failure
These were Clang bugs, which I fixed in r 141777. Updated results for this builder are under the "dgregor" column.
More information about the cfe-dev