[issue26285] Garbage collection of unused input sections from CPython binaries

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26285] Garbage collection of unused input sections from CPython binaries

Changes by Alecsandru Patrascu : -- nosy: +gregory.p.smith, lemburg, scoder, steve.dower, zach.ware ___ Python tracker ___

[issue26285] Garbage collection of unused input sections from CPython binaries

Martin Panter added the comment: Maybe I am missing something, but I don’t see how you could load your module if it uses PyMem_RawMalloc. Perhaps PyMem_RawMalloc has been removed from some other executable (e.g. Parser/pgen), rather than the main Python executable? -- nosy:

[issue26285] Garbage collection of unused input sections from CPython binaries

Alecsandru Patrascu added the comment: I've done again the experiments on larger workloads, such as our OpenStack Swift cluster, and it works without any issues. Also, I've attached an archive with a simple external module in CPython3 that uses PyMem_RawMalloc. The output is ok, and it's

[issue26285] Garbage collection of unused input sections from CPython binaries

Antoine Pitrou added the comment: Le 04/02/2016 21:42, Alecsandru Patrascu a écrit : > > To compress all of the above, the main reason for this speedup is the > reduction of the code path length and having the useful function > close together, so that the CPU will be able to prefetch them in >

[issue26285] Garbage collection of unused input sections from CPython binaries

STINNER Victor added the comment: > Also any name starting with Py_ or _Py_ is an API that may be called by > third-party code, so it shouldn't be removed at all... Right. You cannot remove the following functions, they are part of the public C API (Include/pymem.h). /usr/bin/ld: Removing

[issue26285] Garbage collection of unused input sections from CPython binaries

Alecsandru Patrascu added the comment: Sure, I attached them as files because they have a lot of lines for posting here (~90 in total). The linker offers the possibility to show what piece of data/functions was removed, but I intentionally omitted it in order not to clutter the build trace.

[issue26285] Garbage collection of unused input sections from CPython binaries

Changes by Alecsandru Patrascu : Added file: http://bugs.python.org/file41809/gc-removed-cpython3.txt ___ Python tracker ___

[issue26285] Garbage collection of unused input sections from CPython binaries

Antoine Pitrou added the comment: I'm surprised about the speedups. Is there a logical reason for them? -- nosy: +pitrou ___ Python tracker ___

[issue26285] Garbage collection of unused input sections from CPython binaries

Changes by Alecsandru Patrascu : Added file: http://bugs.python.org/file41806/cpython3-deadcode-v01.patch ___ Python tracker ___

[issue26285] Garbage collection of unused input sections from CPython binaries

New submission from Alecsandru Patrascu: Hi all, This is Alecsandru from the Dynamic Scripting Languages Optimization Team at Intel Corporation. I would like to submit a patch that enables garbage collection of unused input sections from the CPython2 and CPython3 binaries, by using the

[issue26285] Garbage collection of unused input sections from CPython binaries

Changes by SilentGhost : -- nosy: +benjamin.peterson, brett.cannon, haypo, skrah, yselivanov ___ Python tracker ___

[issue26285] Garbage collection of unused input sections from CPython binaries

Stefan Krah added the comment: I thought this was the usual telco benchmark instability, but with the patch _decimal *does* seem to be faster in other areas, too. -- ___ Python tracker

[issue26285] Garbage collection of unused input sections from CPython binaries

Alecsandru Patrascu added the comment: I realize now that I should have explained a bit more the background of this patch. I'll do this now, for everyone to be clear of what is the effect of those flags. This issue was revealed after running the coverage target over various workloads, for