WeSearch

Type Punning in C and C++

Steve SCHNEPP· ·3 min read · 0 reactions · 0 comments · 2 views
More from Personal Workflow Blog programming Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

Type Punning in C and C++ Sep 21, 2026 • Steve SCHNEPP c undefined-behavior c++ About 7 min read I had a bug that took me a while to track down. A pointer cast worked fine at -O0 and silently broke at -O2. The C vs C++ distinction here is genuinely treacherous, and most blog posts on the topic get it wrong.

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,988 of its stories. Top-voted stories on Hacker News.

Original article
Personal Workflow Blog · Steve SCHNEPP
Read full at Personal Workflow Blog →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherPersonal Workflow Blog
Canonical URLhttps://blog.pwkf.org/2026/09/21/correct-type-punning-in-c.html
Publication timeTue, 22 Sep 2026 11:29:47 +0000
Retrieval time2026-09-22T11:53:50.953Z
Last seen2026-09-22T11:53:50.953Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterNone
Cluster logicNot yet clustered, or no peer story found in the clustering window.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Type Punning in C and C++ Sep 21, 2026 • Steve SCHNEPP c undefined-behavior c++ About 7 min read I had a bug that took me a while to track down. The problem was type punning. A pointer cast worked fine at -O0 and silently broke at -O2. The C vs C++ distinction here is genuinely treacherous, and most blog posts on the topic get it wrong. Type punning is interpreting memory as different types between reads and writes. It’s essential for serialisation, network protocols, and low-level hardware access. The problem is that “works in practice” and “has defined behaviour” are different things. The Spectrum from Safe to UB In C, the safe ways to type pun are union and memcpy.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Personal Workflow Blog.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments