https://bugs.kde.org/show_bug.cgi?id=466104
Paul Floyd <pjfl...@wanadoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Paul Floyd <pjfl...@wanadoo.fr> ---
I haven't much changed Linux glibc, but just about all the other platforms have
been overhauled.
The behaviour is still static. However it shouldn't be too difficult to
refactor the present code to make it runtime configurable. If ever we do that
then we could have a set of bitmasks that would correspond to things like
VG_MEMALIGN_ALIGN_POWER_TWO (there 1 to 4 per function). Then we could have
either specific options or options like --malloc-lib=tcmalloc (or both).
That would add a bit of overhead - the current code with static macros should
optimize out all the ones that are turned off.
commit e8d4d64e46cde7507c3716ad8094d886e8824fa4 (HEAD -> master, origin/master,
origin/HEAD)
Author: Paul Floyd <pjfl...@wanadoo.fr>
Date: Mon Mar 6 21:50:01 2023 +0100
Bug 466104 - aligned_alloc problems, part 1
I think that these are all now done.
This commit refactors memalign and updates manual-core.xml
to say some behaviour of Valgrind depends on the build time
OS and libraries.
--
You are receiving this mail because:
You are watching all bug changes.
