Krister Walfridsson’s old blog

Random thoughts on programming languages, compilers, operating systems, etc.

Saturday, March 3, 2018

Detecting incorrect C++ STL usage

›
The GCC and LLVM sanitizers are great for finding problems in C++ code, but they do not detect problems with incorrect STL usage. For examp...
1 comment:
Sunday, February 4, 2018

GCC command options for debugging – -Og and -g3

›
I listened to a recent CppCast episode where Balázs Török talked about game development and mentioned that C++ abstractions make the code ...
Sunday, January 21, 2018

GCC back end performance tuning

›
This is part six of a series “ Writing a GCC back end ”. Cost model – TARGET_RTX_COSTS The compiler often has different options for ho...
1 comment:
Tuesday, December 12, 2017

More about GCC instruction patterns

›
This is part five of a series “ Writing a GCC back end ”. The previous post about GCC’s low-level IR did only contain the minimum to g...
6 comments:
Sunday, October 29, 2017

Excessive GCC memory usage for large std::bitset arrays

›
The C++ slack channel had a discussion last week about the code #include <array> #include <bitset> #include <cstddef>...
2 comments:
Saturday, September 16, 2017

Useful GCC warning options not enabled by -Wall -Wextra

›
Note: This blog post was written for GCC 7. Later versions of the compiler may have added some of these warnings to -Wall or -Wextra . ...
16 comments:
Friday, September 8, 2017

Follow-up on “Why undefined behavior may call a never-called function”

›
I have recieved several questions on the previous blog post about what happens for more complex cases, such as #include <cstdlib> ...
7 comments:
Monday, September 4, 2017

Why undefined behavior may call a never-called function

›
My twitter feed has recently been filled with discussions about the following program #include <cstdlib> typedef int (*Function)...
5 comments:
‹
›
Home
View web version
Powered by Blogger.