This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [v3] c++0x <mutex> and <condition_variable>
On Wed, Sep 3, 2008 at 3:37 PM, Chris Fairles <chris.fairles@gmail.com> wrote:
> On Wed, Sep 3, 2008 at 3:21 PM, _ZSt15__once_callable;Kosnik
> <bkoz@redhat.com> wrote:
>>
>>> Committed after a multilib build on x86_64-linux.
>>
>> No big deal, but two new fails due to missing symbols on x86_64/linux:
>>
>>
>> FAIL: 30_threads/call_once/call_once1.cc (test for excess errors)
>> WARNING: 30_threads/call_once/call_once1.cc compilation failed to
>> produce executable
>>
>> /mnt/share/bld/gcc/x86_64-unknown-linux-gnu/libstdc++-v3/include/mutex:639:
>> undefined reference to `std::__once_callable' /tmp/cc0eXVGO.o: In
>> function `call_once<void (*)(int),
>> int>': /mnt/share/bld/gcc/x86_64-unknown-linux-gnu/libstdc++-v3/include/mutex:654:
>> int>undefined reference to
>> int>`std::__once_callable' /mnt/share/bld/gcc/x86_64-unknown-linux-gnu/libstdc++-v3/include/mutex:655:
>> int>undefined reference to `std::__once_call'
>> /tmp/cc0eXVGO.o: In function `__gthread_once':
>> /mnt/share/bld/gcc/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu/bits/gthr-default.h:718:
>> undefined reference to `__once_proxy'
>>
>> FAIL: 30_threads/condition_variable_any/cons/1.cc (test for excess
>> errors) WARNING: 30_threads/condition_variable_any/cons/1.cc
>> compilation failed to produce executable
>>
>> /mnt/share/src/gcc/libstdc++-v3/testsuite/30_threads/condition_variable_any/cons/1.cc:45:
>> undefined reference to
>> `std::condition_variable_any::condition_variable_any()' /mnt/share/src/gcc/libstdc++-v3/testsuite/30_threads/condition_variable_any/cons/1.cc:45:
>> undefined reference to
>> `std::condition_variable_any::~condition_variable_any()
>>
>
> All those symbols are in gnu.ver I think:
> _ZSt11__once_call;
> _ZSt15__once_callable;
> __once_proxy;
> _ZNSt22condition_variable_anyC1Ev;
> _ZNSt22condition_variable_anyC2Ev;
> _ZNSt22condition_variable_anyD1Ev;
> _ZNSt22condition_variable_anyD2Ev;
>
> Maybe the once_call stuff has something to do with _GLIBCXX_HAVE_TLS ?
> The condvar_any, not sure.
>
Paolo, I noticed something else, some testcases seem to be missing:
30_threads/recursive_mutex/lock/*
30_threads/recursive_mutex/try_lock/*
30_threads/recursive_mutex/unlock/*
Chris