News for hackers. Stuff that matters.
Re:totally_safe_transmute, Line-by-Line (2021) by aw1621107 on Tuesday January 09, 2024 @03:32AM (#38923722)
> Not by my interpretation of n3096 (April 2023 ISO C draft).

What clause(s) support the claim that that example is UB? At least at first glance it looks pretty similar to the sometimes-recommended way to perform safe type-punning in C, and the only way to "directly" invoke UB via memcpy (passing pointers to overlapping objects) isn't relevant here.

The only suspicious part to me is the size/number of bytes to copy, but I'm not sure that's outright UB?

Re:totally_safe_transmute, Line-by-Line (2021) by kazinator on Tuesday January 09, 2024 @04:09AM (#38923917)
We have no idea whether the bytes that were copied into that object are a valid representation.
Re:totally_safe_transmute, Line-by-Line (2021) by aw1621107 on Wednesday January 10, 2024 @10:58AM (#38939978)
Ah, I didn't think of that.

That being said, is there a representation for doubles that could be considered invalid? I thought all double bit patterns are interpretable as a "valid" double, even if you get NaNs.