Arlen Keshabyan

You can test it on Windows using MinGW GCC. You can get it from here: [https://gcc-mcf.lhmouse.com](https://gcc-mcf.lhmouse.com)

Please, keep in mind. If you're really going to use atomic then avoid using ++ operator on the atomic variables directly. This is because ++ operator uses fetch_add with the...

Hello Aleksey, Unfortunately, I've been unable to re-scale an image with my thread pool. The result is the striped picture:  But it's good when re-scaled with a single thread:...

Here is the library that I use (attached to the message). [thread_pool.txt](https://github.com/avaneev/avir/files/3511722/thread_pool.txt) Just rename it to *.hpp

The thread pool is utilized like this: ``` nstd::avir_scale_thread_pool scaling_pool; nstd::avir::CImageResizerVars vars; vars.ThreadPool = &scaling_pool; nstd::avir::CImageResizerParamsUltra roptions; nstd::avir::CImageResizer image_resizer { 8, 0, roptions}; image_resizer.resizeImage(image, width, height, 0, new_image.get(), new_width, new_height,...

Removing tasks didn't help: ``` virtual void removeAllWorkloads() { _tasks.clear(); } ```

It does. It returns the right number of cores.

the size of pool: 16 Workload... Workload... Workload... Workload... Workload... Workload... Workload... Workload... Workload... Workload... Workload... Workload... Workload... Workload... Workload...

It prints 15 times...

I changed the default value from: ``` std::max(std::thread::hardware_concurrency(), 2u) - 1u ``` to ``` std::max(std::thread::hardware_concurrency(), 2u) ``` It didn't change anything. The picture is still striped.