cf5-opt is configured for windows.

_.cpp is updated for more options.
Also a test is done on implicite copy constructor generation for a derived
class.
This commit is contained in:
2013-06-22 22:55:32 +04:00
parent 543a2948a7
commit 58b05cd1f4
4 changed files with 145 additions and 22 deletions

View File

@@ -1,7 +1,8 @@
/* Check cf5-opt.vim defs.
VIM: let g:lcppflags="-std=c++11 -O2"
VIM: let g:cppflags=g:tbb." -ltbbmalloc -ltbbmalloc_proxy"
VIM: let g:ldlibpath=g:tbbld
VIM: let g:lcppflags="-std=c++11 -O2 -pthread"
VIM: let g:cppflags=g:Iboost.g:Itbb
VIM: let g:ldflags=g:Lboost.g:Ltbb.g:tbbmalloc
VIM: let g:ldlibpath=g:Bboost.g:Btbb
*/
#include <tbb/enumerable_thread_specific.h>
#include <tbb/task_scheduler_init.h>
@@ -10,11 +11,20 @@ VIM: let g:ldlibpath=g:tbbld
#include <exception>
#include <vector>
/*
* Conclusion:
* The first task_sheduler_init is configuring number of threads in
* the thread pool. If the task scheduler initialised implicitly then
* the number of threads is the number of cores. To ensure uncomment
* the commented line below.
*/
int main ( void )
{try{
std::vector<int> v(1024*1024*1024);
tbb::task_scheduler_init init3(20);
std::vector<int> v(1024*1024);
//tbb::enumerable_thread_specific<int> count;
tbb::task_scheduler_init init3(5);
tbb::task_scheduler_init init(10);
tbb::task_scheduler_init init2(1);
tbb::enumerable_thread_specific<int> count;