Sujet : Re: A Famous Security Bug
De : chris.m.thomasson.1 (at) *nospam* gmail.com (Chris M. Thomasson)
Groupes : comp.lang.cDate : 24. Mar 2024, 20:45:45
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <utpvta$hvrl$2@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
User-Agent : Mozilla Thunderbird
On 3/24/2024 9:02 AM, Kaz Kylheku wrote:
On 2024-03-24, David Brown <david.brown@hesbynett.no> wrote:
On 24/03/2024 06:50, Kaz Kylheku wrote:
[...]
In safety critical coding, we might want to conduct a code review of
the disassembly of an object file (does it correctly implement the
intent we believe to be expressed in the source), and then retain that
exact file until wit needs to be recompiled.
Before C/C++ 11, I was really worried about a hyper aggressive LTO messing around with my special ASM code for thread sync. So I would examine the disassembly. One alteration could break it! The problem is that it might not break right now... But a year from now wrt running for extended periods of time. If a little shit LTO messed with my externally assembled functions, assembled into an .o and linked in, will, it could create a ticking time bomb of very subtle race conditions...
NOT GOOD!
[...]
Re: A Famous Security Bug
Re: A Famous Security Bug