March Report from #EconomistIntelligenceUnit assessed net #support for #Russia had grown in yr since #invasion of #Ukraine as #Moscow ramps up its courtship of previously #neutral or #geopolitically #unaligned countries. Assessing countries’ enforcement of #sanctions, UN voting patterns, domestic political trends, official statements alongside econ, political, mil, historical ties, EIU determined that past yr saw increase in countries leaning toward Russia from 25 to 36.https://www.eiu.com/n/russias-pockets-of-support-are-growing-in-the-developing-world/

As if developing #KF on an old #Core2Duo laptop wasn't bad enough (over 30minutes to build, have to use -j1 due to insufficient RAMs), it crashes with #SIGILL #IllegalInstruction on #vmovups which seems to be an #AVX instruction (CPU is so old it does not support it).

Retrying the build with `-march=native`, but I recall submitting a #GCC patch to #Debian to replace #aligned moves with #unaligned ones, so maybe I broke it all by myself (the stack on #Windows is only 16byte aligned...).

Ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939559

Turns out is an upstream #GCC #bug that hasn't been fixed despite being reported in 2012. Windows 64bit #stack is aligned to 16 bytes only, and some part of GCC generates vector move instructions that require 32 bytes. Problem doesn't occur on Linux as stack can be re-aligned there, some Windows-specific stuff I don't understand means that that isn't possible there.

Currently rebuilding gcc-mingw-w64 Debian package with an #HorribleHack to replace all #aligned #vector #move to #unaligned vector move in the i386+mmx+sse machine descriptions.