[valgrind] [Bug 473944] Handle mold linker split RW PT_LOAD segments correctly

2023-09-01 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=473944 Philippe Waroquiers changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[valgrind] [Bug 473944] Handle mold linker split RW PT_LOAD segments correctly

2023-08-31 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473944 --- Comment #4 from Paul Floyd --- I also think that it's better to have less hard coded assumptions about the number of PT_LOAD segments. This makes one part more flexible. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 473944] Handle mold linker split RW PT_LOAD segments correctly

2023-08-31 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=473944 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet.

[valgrind] [Bug 473944] Handle mold linker split RW PT_LOAD segments correctly

2023-08-30 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473944 --- Comment #2 from Paul Floyd --- With the patch I get one regression failure helgrind/tests/pth_destroy_cond (stderr) There is missing source information, presumably due to a failure reading debuginfo. The first aspacem map is --54635:1:

[valgrind] [Bug 473944] Handle mold linker split RW PT_LOAD segments correctly

2023-08-30 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473944 --- Comment #1 from Paul Floyd --- (In reply to Philippe Waroquiers from comment #0) I really don't understand what linker writers are doing. First they split the RW PT_LOAD into 2 which I thought was for performance, putting infrequently accessed

[valgrind] [Bug 473944] Handle mold linker split RW PT_LOAD segments correctly

2023-08-30 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473944 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this