default threads on

[ringabout]

No description provided.

[arnetheduck]

ooh, nice :) I hope there's progress here, tried it back in #10781 and it was .. difficult.

[ringabout]

tried it back in #10781 and it was .. difficult.

Quite so, I hope I can manage it eventually.

[ringabout]

CI failure is partialy caused by #19372

[SolitudeSF]

in some cases enabling threads give up to 5% performance hit in singlethread applications. is this just accepted?

[ringabout]

Hi, it was discussed here: nim-lang/RFCs#361 and listed as the roadmap for 2.0: nim-lang/RFCs#437

IMO, it can hurt the performance of single-threaded application, they can use threads:off to mitigate the affects.

[ringabout]

I have made PRs to nitter and nim-plotly => SciNim/nim-plotly#82 and zedeus/nitter#662

[dom96]

Does --threads:on imply a new DLL dependency? I saw a new user having trouble with nimsuggest because of missing libwinpthread-1.dll: dom96/choosenim#298.

[cheatfate]

If std or choosenim uses one of this procedures on Windows

clock_getres
clock_gettime
clock_nanosleep
clock_settime
nanosleep
pthread_attr_destroy
pthread_attr_getdetachstate
pthread_attr_getinheritsched
pthread_attr_getschedparam
pthread_attr_getschedpolicy
pthread_attr_getscope
pthread_attr_getstack
pthread_attr_getstackaddr
pthread_attr_getstacksize
pthread_attr_init
pthread_attr_setdetachstate
pthread_attr_setinheritsched
pthread_attr_setschedparam
pthread_attr_setschedpolicy
pthread_attr_setscope
pthread_attr_setstack
pthread_attr_setstackaddr
pthread_attr_setstacksize
pthread_barrier_destroy
pthread_barrier_init
pthread_barrier_wait
pthread_barrierattr_destroy
pthread_barrierattr_getpshared
pthread_barrierattr_init
pthread_barrierattr_setpshared
pthread_cancel
pthread_cond_broadcast
pthread_cond_destroy
pthread_cond_init
pthread_cond_signal
pthread_cond_timedwait
pthread_cond_timedwait_relative_np
pthread_cond_wait
pthread_condattr_destroy
pthread_condattr_getclock
pthread_condattr_getpshared
pthread_condattr_init
pthread_condattr_setclock
pthread_condattr_setpshared
pthread_create
pthread_create_wrapper
pthread_delay_np
pthread_detach
pthread_equal
pthread_exit
pthread_get_concurrency
pthread_getclean
pthread_getconcurrency
pthread_getevent
pthread_gethandle
pthread_getname_np
pthread_getschedparam
pthread_getspecific
pthread_join
pthread_key_create
pthread_key_delete
pthread_kill
pthread_mutex_destroy
pthread_mutex_init
pthread_mutex_lock
pthread_mutex_timedlock
pthread_mutex_trylock
pthread_mutex_unlock
pthread_mutexattr_destroy
pthread_mutexattr_getprioceiling
pthread_mutexattr_getprotocol
pthread_mutexattr_getpshared
pthread_mutexattr_gettype
pthread_mutexattr_init
pthread_mutexattr_setprioceiling
pthread_mutexattr_setprotocol
pthread_mutexattr_setpshared
pthread_mutexattr_settype
pthread_num_processors_np
pthread_once
pthread_rwlock_destroy
pthread_rwlock_init
pthread_rwlock_rdlock
pthread_rwlock_timedrdlock
pthread_rwlock_timedwrlock
pthread_rwlock_tryrdlock
pthread_rwlock_trywrlock
pthread_rwlock_unlock
pthread_rwlock_wrlock
pthread_rwlockattr_destroy
pthread_rwlockattr_getpshared
pthread_rwlockattr_init
pthread_rwlockattr_setpshared
pthread_self
pthread_set_concurrency
pthread_set_num_processors_np
pthread_setcancelstate
pthread_setcanceltype
pthread_setconcurrency
pthread_setname_np
pthread_setschedparam
pthread_setspecific
pthread_spin_destroy
pthread_spin_init
pthread_spin_lock
pthread_spin_trylock
pthread_spin_unlock
pthread_testcancel
pthread_timechange_handler_np
pthread_tls_init
sched_get_priority_max
sched_get_priority_min
sched_getscheduler
sched_setscheduler
sched_yield
sem_close
sem_destroy
sem_getvalue
sem_init
sem_open
sem_post
sem_post_multiple
sem_timedwait
sem_trywait
sem_unlink
sem_wait

It will require this DLL. But usually you should avoid usage of posix_ pthread_ functions on Windows.

[dom96]

Does enabling --threads mean that one of those functions is used?

[dom96]

Yep, it does. I compiled a simple hello world with and without --threads:on:

This means --threads:on on Windows adds an implicit DLL dependency. On my system this actually breaks this simple hello world example because it grabs an x86 libwinpthread from my Android SDK install.

[ghost]

@dom96 to be fair this DLL is not added as a dependency if the C compiler uses native Windows threads like VCC or statically link winpthread like tdm-gcc