<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mesh: Compacting Memory Management for C/C++ Applications · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1902.04738/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1902.04738/feed.xml" rel="self" type="application/rss+xml" /><item><title>Mesh: Compacting Memory Management for C/C++ Applications — mentioned by superjan</title><link>https://news.ycombinator.com/item?id=42665511</link><guid isPermaLink="false">urn:hackerpapers:mention:1902.04738:42665511</guid><pubDate>Sat, 11 Jan 2025 12:48:42 GMT</pubDate><description>&lt;p&gt;There’s a great paper from the group of Emery Berger, where they merge memory pages that become sparse. A kind of garbage collection for C and C++ languages. There’s also a good presentation about it on youtube. https://arxiv.org/abs/1902.04738 The presentation: https://youtu.be/c1UBJbfR-H0&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1902.04738/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Mesh: Compacting Memory Management for C/C++ Applications — mentioned by verdagon</title><link>https://news.ycombinator.com/item?id=36694868</link><guid isPermaLink="false">urn:hackerpapers:mention:1902.04738:36694868</guid><pubDate>Wed, 12 Jul 2023 14:14:01 GMT</pubDate><description>&lt;p&gt;In the basic generational references approach that was a drawback, and the reason it couldn&amp;#x27;t release memory back to the OS. We planned to use something like MESH [0] to reduce the fragmentation. We created two newer approaches since then, which let any memory be reused for any purpose: * Random generational references, where it&amp;#x27;s fine if generations overlap with other data. * Side-table generations, which is slower but we keep the generations in a side-table. It&amp;#x27;s can be seen in old 0.1 versions as the &amp;quot;resilient-v2&amp;quot; mode, and I plan on resurrecting it for unrelated reasons. The former will…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1902.04738/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Mesh: Compacting Memory Management for C/C++ Applications — HN submission</title><link>https://news.ycombinator.com/item?id=29318598</link><guid isPermaLink="false">urn:hackerpapers:submission:1902.04738:29318598</guid><pubDate>Tue, 23 Nov 2021 15:04:25 GMT</pubDate><description>&lt;p&gt;Mesh: Compacting Memory Management for C/C++ Applications&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;3 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1902.04738/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Mesh: Compacting Memory Management for C/C++ Applications — HN submission</title><link>https://news.ycombinator.com/item?id=27399047</link><guid isPermaLink="false">urn:hackerpapers:submission:1902.04738:27399047</guid><pubDate>Fri, 04 Jun 2021 21:03:12 GMT</pubDate><description>&lt;p&gt;Mesh: Compacting Memory Managementfor C/C++ Applications&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;3 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1902.04738/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Mesh: Compacting Memory Management for C/C++ Applications — mentioned by moonchild</title><link>https://news.ycombinator.com/item?id=27013365</link><guid isPermaLink="false">urn:hackerpapers:mention:1902.04738:27013365</guid><pubDate>Sun, 02 May 2021 08:31:12 GMT</pubDate><description>&lt;p&gt;Actually...https://arxiv.org/pdf/1902.04738.pdf On a more serious note, most c programs I see don&amp;#x27;t do very much of that, preferring to allocate fixed-size buffers on the stack. Additionally, most GC&amp;#x27;d languages that aren&amp;#x27;t java have crappy GCs, and those GC&amp;#x27;d languages that are java lack value types. This harms spatial locality quite a bit, and compaction can&amp;#x27;t fully compensate for that. They are working on adding value types to the jvm, though; it will be very interesting to see how performance changes. (I expect not very much in practice—those projects for which performance was important…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1902.04738/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Mesh: Compacting Memory Management for C/C++ Applications — mentioned by vanderZwan</title><link>https://news.ycombinator.com/item?id=19979103</link><guid isPermaLink="false">urn:hackerpapers:mention:1902.04738:19979103</guid><pubDate>Wed, 22 May 2019 08:30:19 GMT</pubDate><description>&lt;p&gt;Looks like he reinvented shuffle vectors on his own. I think a lot of people have over the years, but crazy enough nobody bothered to publish it until February this year! Maybe it felt too intuitive? [0] https://observablehq.com/@jobleonard/shuffle-vectors [1] https://arxiv.org/abs/1902.04738&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1902.04738/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Mesh: Compacting Memory Management for C/C++ Applications — mentioned by sanxiyn</title><link>https://news.ycombinator.com/item?id=19866552</link><guid isPermaLink="false">urn:hackerpapers:mention:1902.04738:19866552</guid><pubDate>Thu, 09 May 2019 09:05:26 GMT</pubDate><description>&lt;p&gt;Fragmentation is solvable. Mesh can compact C programs using malloc/free without any source changes. https://arxiv.org/abs/1902.04738&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1902.04738/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item><item><title>Mesh: Compacting Memory Management for C/C++ Applications — HN submission</title><link>https://news.ycombinator.com/item?id=19182779</link><guid isPermaLink="false">urn:hackerpapers:submission:1902.04738:19182779</guid><pubDate>Sun, 17 Feb 2019 05:12:54 GMT</pubDate><description>&lt;p&gt;Mesh: Compacting Memory Management for C/C++ Applications&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;167 points; 36 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1902.04738/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
