<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MLGO: a Machine Learning Guided Compiler Optimizations Framework · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2101.04808/</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/2101.04808/feed.xml" rel="self" type="application/rss+xml" /><item><title>MLGO: a Machine Learning Guided Compiler Optimizations Framework — mentioned by boomanaiden154</title><link>https://news.ycombinator.com/item?id=40824997</link><guid isPermaLink="false">urn:hackerpapers:mention:2101.04808:40824997</guid><pubDate>Fri, 28 Jun 2024 20:34:57 GMT</pubDate><description>&lt;p&gt;I would not say we are anywhere close to perfect in compilation. Even just looking at inlining for size, there are multiple recent studies showing ~10+% improvement (https://dl.acm.org/doi/abs/10.1145/3503222.3507744, https://arxiv.org/abs/2101.04808). There is a massive amount of headroom, and even tiny bits still matter as ~0.5% gains on code size, or especially performance, can be huge.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2101.04808/"&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>MLGO: a Machine Learning Guided Compiler Optimizations Framework — mentioned by boomanaiden154</title><link>https://news.ycombinator.com/item?id=37552865</link><guid isPermaLink="false">urn:hackerpapers:mention:2101.04808:37552865</guid><pubDate>Mon, 18 Sep 2023 06:19:42 GMT</pubDate><description>&lt;p&gt;What&amp;#x27;s the benefit of having an LLM do those things in a way that guesstimates? There are big wins to be had in code-size and some wins to be had in performance related to inlining [1][2], but I think the implementation in the references directly tied into the compiler&amp;#x27;s inlining heuristic is a much better way to do that as it guarantees correctness. In addition, there&amp;#x27;s a reason that compilers basically ignore the `inline` keyword these days. For branch reordering, techniques like BOLT [5] are pretty effectively able to reorder code layout at the binary level for big performance gains by…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2101.04808/"&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>MLGO: a Machine Learning Guided Compiler Optimizations Framework — mentioned by boomanaiden154</title><link>https://news.ycombinator.com/item?id=37550346</link><guid isPermaLink="false">urn:hackerpapers:mention:2101.04808:37550346</guid><pubDate>Sun, 17 Sep 2023 23:21:24 GMT</pubDate><description>&lt;p&gt;For function inlining specifically, I&amp;#x27;m not sure LLMs are necessarily the right choice. The original MLGO paper [1] demonstrated a big code-size improvement with a ML model for making inlining decisions (7-20% code size wins), but they used tens of engineered features. Maybe a LLM could squeeze some additional size wins out, but maybe not [2]. Additionally, there are other factors to consider when productionizing these systems. Compile time is important (which LLMs will almost certainly explode), and anyone concerned about code size will probably be doing (Thin)LTO which would require feeding…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2101.04808/"&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>MLGO: a Machine Learning Guided Compiler Optimizations Framework — HN submission</title><link>https://news.ycombinator.com/item?id=36959531</link><guid isPermaLink="false">urn:hackerpapers:submission:2101.04808:36959531</guid><pubDate>Tue, 01 Aug 2023 17:43:21 GMT</pubDate><description>&lt;p&gt;MLGO: A Machine Learning Guided Compiler Optimizations Framework (2021)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2101.04808/"&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>MLGO: a Machine Learning Guided Compiler Optimizations Framework — mentioned by compiler-guy</title><link>https://news.ycombinator.com/item?id=36959512</link><guid isPermaLink="false">urn:hackerpapers:mention:2101.04808:36959512</guid><pubDate>Tue, 01 Aug 2023 17:42:14 GMT</pubDate><description>&lt;p&gt;There is a fair amount of academic research on this topic. Eg, MLGO[1], but I don&amp;#x27;t know of any being used for production work. 1. https://arxiv.org/pdf/2101.04808.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2101.04808/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
