[Bug c/116854] New: GCC incorrectly assumes all CPUs where -march=native resolves to -march=bdver4 will have RDRND support

2024-09-26 Thread ipsum.te.futue at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116854 Bug ID: 116854 Summary: GCC incorrectly assumes all CPUs where -march=native resolves to -march=bdver4 will have RDRND support Product: gcc Version: 13.3.1 Status: UNCON

[Bug target/116854] GCC incorrectly assumes all CPUs where -march=native resolves to -march=bdver4 will have RDRND support

2024-09-26 Thread ipsum.te.futue at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116854 --- Comment #8 from Anonymous --- (In reply to Thiago Macieira from comment #5) > This has nothing to do with -march=native. In fact, for the Gentoo people > who are using -march=native, everything is fine because __RDRND__ is *not* > defined (

[Bug target/116854] GCC incorrectly assumes all CPUs where -march=native resolves to -march=bdver4 will have RDRND support

2024-09-26 Thread ipsum.te.futue at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116854 --- Comment #7 from Anonymous --- (In reply to Thiago Macieira from comment #5) > This has nothing to do with -march=native. In fact, for the Gentoo people > who are using -march=native, everything is fine because __RDRND__ is *not* > defined (