<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Intel MPX Explained: An Empirical Study of Intel MPX and Software-based Bounds Checking Approaches · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1702.00719/</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/1702.00719/feed.xml" rel="self" type="application/rss+xml" /><item><title>Intel MPX Explained: An Empirical Study of Intel MPX and Software-based Bounds Checking Approaches — mentioned by saagarjha</title><link>https://news.ycombinator.com/item?id=21626731</link><guid isPermaLink="false">urn:hackerpapers:mention:1702.00719:21626731</guid><pubDate>Mon, 25 Nov 2019 09:57:19 GMT</pubDate><description>&lt;p&gt;Apparently MPX had a number of issues in general that made it worse than tools like Address Sanitizer: https://arxiv.org/pdf/1702.00719.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1702.00719/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
