Yay!! Again, some compiler decided to change template conversion operator rules.
And again, compilers won't agree with what the standard says or with each other since changing the rules may break users, even though they keep doing it (even in minor versions!) 🤦
/home/build/repo/compat_vis.c: In function ‘stravis’:
/home/build/repo/compat_vis.c:222:23: warning: pointer ‘buf_15’ may be used after ‘realloc’ [-Wuse-after-free]
222 | *outp = buf;
| ~~~~~~^~~~~
/home/build/repo/compat_vis.c:220:17: note: call to ‘realloc’ here
220 | *outp = realloc(buf, len + 1);
| ^~~~~~~~~~~~~~~~~~~~~
I do not understand why, the code looks correct... What am I missing?
Learning about the gcc attribute ((ifunc ("resolve_xxx"))) construct is making me wonder what the hell the person who thought it up was drinking, smoking or eating, and the code review team too.
I'm struggling to think of a reasonable usecase for this monstrosity of a construct.
When moving to a compiler like #tcc from #gcc and #clang , what speed pitfalls should I be aware of that optimizations in those compilers typically hold our hand with, but tcc does not?
I have half an hour trip to climbing gym and back 3 times a week. Not to waste this time I take my laptop with downloaded materials with me and watch courses.
New vulnerability exposed on GCC. @Azeria and Tom Hebb, has discovered a brand new 0-day in GCC. On GCC's AArch64 version, stack protection doesn't detect overflows of dynamically-sized local variables. Vulnerability fixed! But there are a lot of binaries in the wild which has this vulnerability.
While a few years late compared to many other open-source projects adopting a Code of Conduct, the GCC Steering Committee has now adopted a Code of Conduct 'CoC' for this open-source compiler project.
Extremely impressed by #GCC 14.1 static analysis (-fanalyzer). Not only really finding real bugs but enough information to convince oneself of the reality of the issue. A bit frightening on an old codebase.
"Modern C compilers already have the ability to be memory-safe, we just need to make minor -- and compatible -- changes to turn it on. Instead of a hard-fork that abandons legacy system, this would be a soft-fork that enables memory-safety for new systems."
En el episodio de hoy de #yavosotrosque , abro mi VM con windows10, porque es sábado y tengo el cuerpo para full-contact y microsoft me dice que para que no me vuelva a congelar mis ficheros en OneDrive que borre, o compre más capacidad...
Tengo 0.1% ocupado. Creo que tengo un fichero de texto, o dos.
I spent ~hour yesterday fighting an issue with my C++ code, only to later figure out it's a possible GCC bug, because Clang accepts the same code.
The issue is that GCC does not permit a constrained type parameter in a template template parameter of an aliased template. See the simplified code with the issue.
A cursory search of GCC Bugzilla does not readily show any related bug. I'll look carefully but lemme know if this is a known bug (probably is). 🙏🏽
GCC Adopts A Code of Conduct (www.phoronix.com)
While a few years late compared to many other open-source projects adopting a Code of Conduct, the GCC Steering Committee has now adopted a Code of Conduct 'CoC' for this open-source compiler project.