Created attachment 840891 [details] gcc build log on skylake sys-devel/gcc:12[jit] build on skylake with -march=core2 -mtune=core works fine on targeted system as long as libgccjit is not involved. libgccjit runs fine on targeted system, but generates skylake class instructions. When applying test in app-editors/emacs build log, ibgccjit is somehow core2 compliant as binary is build. This binary fails to run on core2, but runs fine on skylake.
Created attachment 840893 [details] app-editors/emacs build log on core2 target
Created attachment 840895 [details] binary generated on target, working only on gcc building host
Related forums post: https://forums.gentoo.org/viewtopic-t-1159653.html
https://gcc.gnu.org/onlinedocs/jit/internals/index.html#environment-variables Shows how things are hardcoded in libgccjit. That makes things a little harder when trying to workaround by replacement from other distro binaries. That could plead for stage3 to add sys-devel/gcc USE=jit. It would at least fit my use case ;) Thks 4 the gcc.gnu.org links, although they suggest how things are unlikely to happen any soon :(
Binary package has been made available here: https://gitlab.com/gentoo-pdm/sys-devel/gcc/pdm-gcc/gcc-12-core2-compatible-binary-package Hopefully repository is in public access. Plz let me know if isn't.
Albeit there was no rationale to do so, I've updated target to gcc-12.2.1_p20221210 built using core2 profiled gcc-12.2.1_p20221203 on skylake host. It so happened the above reported failing sequence hence succeeded. I don't see any host portage env changes, manual or upstream, that would explain this new result, besides the use of a core2 targeted compilter to build
Sorry, something borked while typing in here... ... of a core2 targeted compiler to build a core2 targeted compiler upgrade. stable portage has been upgraded on 2022-12-09, but I doubt it played any role in the fix. Will retry to build core2 targeted from skylake build just to make sure bug is real. Happy to close now, and ready to build app-editors/emacs[jit] on an over a decade old laptop.
It so happened here after building twice in a row gcc-12.2.1_p20221203.tbz2 with -march=core2 -mtune=core2 on a skylake host, I forgot to reinstall its -march=native -mtune=native build. Consequently a single pass pass upgrade to 12.2.1_p20221224 with -march=native -mtune=native on that same skylake host should provide a libgccjit that generates binaries with core2 level instructions. I did the test generating a binary with the new libgccjit on the skylake and tried to run it on a core2 CPU where it executed fine. So the hypothesis for 2 passes to build a libgccjit that matches -march!=native -mtune!=native with a gcc build with -march=native -mtune=native is getting confirmed here. For that reason I propose to cancel RESOLVED to let a wider scope to the issue. I have no idea if that issue is package related or upstream related. jit feature issues seems to have a low -P3 as of this writing.
