TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Refined Input, Degraded Output: The Counterintuitive World of Compiler Behavior

64 点作者 matt_d11 个月前

2 条评论

AgentOrange123411 个月前
This seems neat in a couple of ways. It’s a lot like fuzzing or property-based testing, but those approaches usually target crashes or try to catch functional bugs. This feels like a way to do fuzzing for performance or other kinds of quality. The idea is straightforward, but it’s impressive to me that this can be practically implemented and used at the scale of real languages and compilers.<p>As a vaguely related similar idea, once upon a time at a hardware company we had a regression suite that failed if our chip was less performant than a competitor’s. But that test suite was largely hand crafted. The ability to generate these cases randomly is super cool.
rurban11 个月前
Catching optimizer bugs, good!<p>It even git bisects to the commit introducing a regression