2019-12-29 13:55:02 -0600 | answered a question | Just linking to opencv ruins thread-concurrency!? Thanks to the answer of 'robin' above, it became clear to me that the true culprit was openblas. Further googling rapidl |
2019-12-29 09:37:52 -0600 | commented answer | Just linking to opencv ruins thread-concurrency!? Thanks for responding! As a matter of fact, I had given up on openCV, for the problems mentioned. I read your post only |
2019-11-07 09:51:37 -0600 | commented question | Just linking to opencv ruins thread-concurrency!? Have a look at the beginning of my posting. The code launches three different threads. Without linking with opencv the p |
2019-11-04 12:03:01 -0600 | commented question | Just linking to opencv ruins thread-concurrency!? @berak. Well, fair enough. But how does that prevent the concurrency of the 3 threads that are started in the demo progr |
2019-11-03 14:52:20 -0600 | commented question | Just linking to opencv ruins thread-concurrency!? @berak, Why unfair? The program does not use opencv, so I would expect the impact of linking against opencv should not |
2019-11-02 10:08:35 -0600 | commented question | Just linking to opencv ruins thread-concurrency!? @mvuori Good suggestion. I just put the pthread library at the end. It does not change the story. |
2019-11-02 07:27:45 -0600 | asked a question | Just linking to opencv ruins thread-concurrency!? Just linking to opencv ruins thread-concurrency!? in a small program demonstrating C++ threads, I noticed that linking |