Yeah, same here. I wonder if this'd have been caught by ubsan, though.
33 karma · joined October 11, 2020
All opinions etc. expressed here are my own an do not represent the company I work at... You know the drill.
(I tend to prefix PATH with the folder I build it into for the specific project I need it for)
But off the top - No lto support, missing some flags that we use when building drivers, valgrind (cachegrind etc) fail to load symbols, some linker stuff is case senstive etc.
Can also add it to PATH, instead of hardcoding it like op did here.
But it's well worth it in some projects - In my case it shaved over a minute from incremental builds, resulting in sub 10 second builds!
(Alsp note you can cache indexes in gdb by default)
This is great! I really needed this multiple times over the years. Always wanted to compare some data between 2 executions of the same applications with 2 different inputs or 2 revisions of an application. This should really help with triangulation of regressions etc. automatically using a single script within gdb!
Funny enough, this language is actually useful for optimized image processing pipelines, especially when targeting such "uniform" devices.
(I think there was at least one more article by danluu on this subject but this one I remembered by name, having discussed it several times with colleagues when considering using something (sqlite) less ad hoc for temporary data)