thread warning ununsed variable
Hi,
On Boost 1.45 I get a warning message in the condition_variable.hpp
inline void condition_variable::wait(unique_lock<mutex>& m)
{
thread_cv_detail::lock_on_exit
On Thu, Nov 25, 2010 at 5:02 AM, Kraus Philipp
Hi, On Boost 1.45 I get a warning message in the condition_variable.hpp inline void condition_variable::wait(unique_lock<mutex>& m) { thread_cv_detail::lock_on_exit
guard; detail::interruption_checker check_for_interruption(&internal_mutex,&cond); guard.activate(m); int const res=pthread_cond_wait(&cond,&internal_mutex); BOOST_ASSERT(!res); this_thread::interruption_point(); } the res variable isn't used (I compile the code with -O2 option)
I hope you're not requesting removing the assertion :) Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
On 2010-11-25 18:53:23 +0100, Emil Dotchevski said:
On Thu, Nov 25, 2010 at 5:02 AM, Kraus Philipp
wrote: Hi, On Boost 1.45 I get a warning message in the condition_variable.hpp inline void condition_variable::wait(unique_lock<mutex>& m) { thread_cv_detail::lock_on_exit
guard; detail::interruption_checker check_for_interruption(&internal_mutex,&cond); guard.activate(m); int const res=pthread_cond_wait(&cond,&internal_mutex); BOOST_ASSERT(!res); this_thread::interruption_point(); } the res variable isn't used (I compile the code with -O2 option) I hope you're not requesting removing the assertion :)
Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
No, it's only a message for the thread developer. I'm ignoring the warning. Greetings Phil
participants (3)
-
Emil Dotchevski
-
Kraus Philipp
-
Philipp Kraus