Finding and Understanding Bugs in C Compilers (2011) [pdf]

Posted3 months agoActive3 months ago

djoldman

28 points

6 comments

users.cs.utah.eduTechstory

calmpositive

Debate

10/100

Compiler TestingC Programming LanguageSoftware Reliability

Key topics

Compiler Testing

C Programming Language

Software Reliability

The linked paper discusses techniques for finding and understanding bugs in C compilers, and the discussion highlights related tools and methodologies for minimizing and analyzing these bugs.

Snapshot generated from the HN discussion

Discussion Activity

Light discussion

First comment

Peak period

84-90h

Avg / period

Key moments

01Story posted
Sep 27, 2025 at 6:59 AM EDT
3 months ago
Step 01
02First comment
Sep 30, 2025 at 5:21 PM EDT
3d after posting
Step 02
03Peak activity
5 comments in 84-90h
Hottest window of the conversation
Step 03
04Latest activity
Sep 30, 2025 at 8:25 PM EDT
3 months ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (6 comments)

Showing 6 comments

pfdietz

3 months ago

1 reply

The Csmith paper. The follow-on paper about Creduce is also worth reading. Creduce takes valid programs and reduces them to smaller valid programs, using some predicate (does this shell script finish with an error code?). This allows hits by Csmith to be greatly minimized automatically. Maintaining validity during shrinking is the central problem.

wyldfire

3 months ago

2 replies

cvise and llvm-reduce are really good complements to c-reduce. Allows for mechanical reduction without any understanding of how compilers / backends are designed. I've found that it's much quicker to get a fix if I do the reduce before opening the bug.

jcranmer

3 months ago

1 reply

As a compiler developer, if you give me a bug and the source is not reduced, I'm decently likely to tell you to reduce it first before I attempt to take a look at it.

stassats

3 months ago

1 reply

A good strategy if you don't care about fixing bugs.

pfdietz

3 months ago

Still, I try to be polite and reduce the code some before making the bug report. I don't want to come across as lazy and load you (in particular) with work I could have done.

Having said that, reduction can be tricky, and I need to do more work on that with the Common Lisp random tester, so as to allow more language constructs to be in the random code.

pfdietz

3 months ago

Really any tooling that parses things can be used with Creduce. It doesn't even have to be C.

View full discussion on Hacker News

ID: 45394719Type: storyLast synced: 11/20/2025, 4:29:25 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Open link View on HN