Can you test attached patch on your gcc 15.x system with -O3 -march native ? I only changed m2r and r2m cases (considering their names) чт, 19 февр. 2026 г., 23:55 Andrew Randrianasulu <[email protected]>:
чт, 19 февр. 2026 г., 23:33 Andrew Randrianasulu <[email protected]
:
чт, 19 февр. 2026 г., 23:03 Stefan de Konink via Cin < [email protected]>:
Op 19-02-2026 om 8:42 p.m. schreef Andrew Randrianasulu via Cin:
чт, 19 февр. 2026 г., 22:21 Phyllis Smith via Cin <[email protected] gg.org <mailto:[email protected]>>:
Can you try:
CFLAGS="-march=native -O3" CXXFLAGS="-march=native -O3"
./configure
gcc (Gentoo 15.2.1_p20251122 p4) 15.2.1 20251122
Both systems tested are AMD Ryzen 5, and older Athlon X4.
Of course you are right that it errs out with O3 (O2 obviously works). Do you have a recommended fix? -- I can not code in C/C+
but
I can test. I tried looking online for a code solution that I could understand and found nothing that made sense to me.
ChatGPT suggested something very simple just replace the =X with =m
#define mmx_r2m(op, reg, mem) \ __asm__ __volatile__ ( \ #op " %%" #reg ", %0" \ : "=m" (mem) \ : \ : "memory")
May be, I think I moved some of it to =X because it was failing on i586 build
https://github.com/xerpi/SDL-3DS/blob/master/src/render/mmx.h
this one uses "m" in those functions but I am not sure it was always correct.
Another suggestion I found on x264 mail list is to disable -fPIC but not sure if it really good idea.
https://x264-devel.videolan.narkive.com/ILCZiFoz/bug-asm-operand-has-impossi...
Also
https://gcc.gnu.org/onlinedocs/gcc/Simple-Constraints.html
in theory it seems m is stricter than X
But this is assembly, so I am not sure how it all interacts ....
The failing part without-zmpeg I found too.
...does the Cinelerra git work for any of you?
Stefan _______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]