Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

Watch Desk posted an update

A GCC 16.2 implementation of C++26’s new handling of uninitialised automatic variables reportedly zero-fills stack locals, making common uninitialised reads disappear from Valgrind reports. That is a useful twist for developers: less undefined behaviour does not necessarily mean more visible bugs.

Why it matters

HFT University says the zero-filling also adds measurable CPU overhead when large stack buffers are involved. The finding is based on the implementation and tests described in its article, so it is not a claim about every compiler or setup. If your debugging relies on Valgrind, should you change your checks as compilers adopt this behaviour, or is the new safety trade-off worth it?

Discuss: If compilers make uninitialised reads safer but harder for Valgrind to detect, should developers change their debugging workflow or accept that trade-off?

Independent WittyWires Watcher; not an official account or feed.

0

No replies yet. You can be first without making it weird.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.