[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-12-23 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=88 Paul Floyd changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-13 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=88 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr --- Comment #11 from Paul Floyd

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-13 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=88 Paul Floyd changed: What|Removed |Added Attachment #153718|0 |1 is obsolete||

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-13 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=88 --- Comment #9 from Paul Floyd --- Created attachment 153718 --> https://bugs.kde.org/attachment.cgi?id=153718&action=edit patch to set tunable This fixes helgrind/tests/tls_threads But it only adds GLIBC_TUNABLES, it doesn't try to modify an existin

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-13 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=88 --- Comment #8 from Paul Floyd --- I'm having a go at this. Setting GLIBC_TUNABLES isn't too difficult (though I haven't yet added handling when it is already set). glibc version seems a lot harder. In glibc: paulf> nm /lib64/libc.so.6 | grep libc_v

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-12 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=88 --- Comment #7 from Philippe Waroquiers --- (In reply to Paul Floyd from comment #6) > > I think we should check and use the existing hint. Current users of the > > hint > > will/should have the same behaviour whatever the glibc version. > > There is

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-12 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=88 --- Comment #6 from Paul Floyd --- > I think we should check and use the existing hint. Current users of the hint > will/should have the same behaviour whatever the glibc version. There is gnu_get_libc_version(). Now, how to call that without breakin

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-12 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=88 --- Comment #5 from Philippe Waroquiers --- (In reply to Paul Floyd from comment #4) > Thanks for adding me to the CC Philippe. > > If I do this: > export GLIBC_TUNABLES="glibc.pthread.stack_cache_size=0" > > Then helgrind/tests/tls_threads fails with

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-12 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=88 --- Comment #4 from Paul Floyd --- Thanks for adding me to the CC Philippe. If I do this: export GLIBC_TUNABLES="glibc.pthread.stack_cache_size=0" Then helgrind/tests/tls_threads fails with just +--21937:0: sched WARNING: pthread stack cache cannot

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-12 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=88 --- Comment #3 from Philippe Waroquiers --- (In reply to Mark Wielaard from comment #2) > (In reply to Philippe Waroquiers from comment #1) > > In the discussion on valgrind-users mailing list, > > Paul reported tthat: > > 'It looks like "stack_cache_

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-12 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=88 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-12 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=88 Philippe Waroquiers changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving

[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable

2022-11-12 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=88 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet.