[perl #125296] CvFILE on threaded, and gv_fetchfile on all perls,burn mad memory

This ticket could sure use some replies from technical eyes.

My understanding — and please correct me if I'm wrong, bulk88 — is that http://perl5.git.perl.org/perl.git/commitdiff/345d4464184a234301341596f73ee2d3550c9799 (roughly) gets us a few kilobytes of heap saved per file loaded.

To me, this seems to multiply the total number of entity types in the implementation without sufficiently benefiting from the increase in complexity.  That said, the implementation is a place where I am much more likely to listen to outside opinions. ;)  So, please, readers: speak up.

-- 
rjbs

---
via perlbug:  queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=125296

• [perl #125296] CvFILE on threaded, and gv_fetchfile on all perls,burn mad memory by bulk88 via RT
• [perl #125296] CvFILE on threaded, and gv_fetchfile on all perls,burn mad memory by Tony Cook via RT
• [perl #125296] CvFILE on threaded, and gv_fetchfile on all perls,burn mad memory by Tony Cook via RT
• [perl #125296] CvFILE on threaded, and gv_fetchfile on all perls,burn mad memory by Ricardo SIGNES via RT
• Re: [perl #125296] CvFILE on threaded, and gv_fetchfile on allperls, burn mad memory by Tim Bunce
• [perl #125296] CvFILE on threaded, and gv_fetchfile on all perls,burn mad memory by bulk88 via RT
• [perl #125296] CvFILE on threaded, and gv_fetchfile on all perls,burn mad memory by bulk88 via RT
• Re: [perl #125296] CvFILE on threaded, and gv_fetchfile on allperls, burn mad memory by Tim Bunce
• [perl #125296] CvFILE on threaded, and gv_fetchfile on all perls,burn mad memory by Father Chrysostomos via RT