<raptop>
!mission add You design a quad-propellant engine.
<LunchBot>
Added mission: You design a quad-propellant engine.
darsie has quit [Ping timeout: 207 seconds]
Wastl4 has joined #KSPOfficial
Wastl2 has quit [Ping timeout: 190 seconds]
_whitelogger has joined #KSPOfficial
_whitelogger has joined #KSPOfficial
Althego has joined #KSPOfficial
_whitelogger has joined #KSPOfficial
_whitelogger has joined #KSPOfficial
darsie has joined #KSPOfficial
_whitelogger has joined #KSPOfficial
<Mat2ch>
packbart: I was loooong asleep then :)
G4Virus_aka_pa1983 has quit [Remote host closed the connection]
<FLHerne>
.mission add Your new hyper-optimizing compiler determines that part of your code will encounter undefined behaviour in 14 years when a timer overflows, and thus can be disregarded entirely.
<LunchBot>
Added mission: Your new hyper-optimizing compiler determines that part of your code will encounter undefined behaviour in 14 years when a timer overflows, and thus can be disregarded entirely.
<FLHerne>
this sort of thing bugs me sometimes
sandbox has joined #KSPOfficial
<Mat2ch>
Unixtime overflow?
<Mat2ch>
And it's something me fellow developers overlook too often. I put quiet a lot of thinking into counter variables. Coming from microcontrollers I know how to abuse overflowing integers for my purpose.
<FLHerne>
Unintended overflows can be a pain, but I was complaining more about optimizing compilers saying "this is an infinite loop, therefore it's UB, therefore simply ignoring it and emitting no code at all is fine"
<FLHerne>
instead of even a warning in some cases
<FLHerne>
I know there are good reasons such things are hard to distinguish from reasonable optimizations, but as a user it's frustrating
<Mat2ch>
that sounds like a bug to me.
<Mat2ch>
The compiler shouldn't remove an infinite loop