Op 19-02-2026 om 8:42 p.m. schreef Andrew Randrianasulu via Cin:
>
>
> чт, 19 февр. 2026 г., 22:21 Phyllis Smith via Cin <cin@lists.cinelerra-
> gg.org <mailto:cin@lists.cinelerra-gg.org>>:
>
> 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
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.