News for hackers. Stuff that matters.
Re:Bounded Integer: Header-only C++ library replaces integer... by CoolGuySteve on Sunday September 29, 2019 @03:19PM (#21109087)
I feel like that's mostly Microsoft's fault, their STL implementation is super aggressive about checks in debug builds to the point that it becomes sort of useless in heavy use/high performance scenarios. Between that and the lack of valgrind, I'm pretty glad I left that world.

Over in Linux/g++ land, it's not nearly so bad. Bounds errors are mostly handled by address sanitizer such that -O0 performance is decent. And if -O0 is too slow, there's -Og which takes slightly longer to compile and has less information for gdb.

I work almost exclusively in "g++ -O0" until it's time to release.

Clang is decent too, but I find the C++ compile times are atrocious, like almost double for my admittedly template-heavy code. And performance of the compiled output is no better.

Re:Bounded Integer: Header-only C++ library replaces integer... by PirateAvogadro on Monday September 30, 2019 @08:16AM (#21114443)
You could use ITERATOR_DEBUG_LEVEL=1 or 0 in debug mode; I made a "FastDebug" profile for this, although you will have to recompile dependencies
Re:Bounded Integer: Header-only C++ library replaces integer... by makapuf on Sunday September 29, 2019 @03:47PM (#21109249)
Doesn't gcc have -Og that enables some optimizations but leaves the ones that prevent debugging.
Re:Bounded Integer: Header-only C++ library replaces integer... by CoolGuySteve on Sunday September 29, 2019 @04:02PM (#21109318)
It has issues sometimes evaluating inlined expressions, unfortunately.