forked from pool/gcc12
915f26469f
to release my review on the gcc package now. -- - Update to GCC 12.1 release, 1ea978e3066ac565a1ec28a96a4d61, git27 - Bump to 621650f64fb6679c457c33abf27c925f28bddc62, git9 * GCC 12.1 release candidate - Bump to f27848a5dc4d3b16cd4112bddcb59e0916eba623, git192706. - Switch ppc64le to the IEEE long double ABI by default in Factory. - Separate ppc64le from ppc/ppc64 specific configury. - Add _multibuild to gather all .spec files and reduce the number of .changes files to one, autogenerated by change_spec. - Drop %ringdisabled handling. - Ada bootstrap now requires at least GCC 5, use GCC 7 on SLES 12 instead of GCC 4.8. - Drop no longer necessary gcc12-d-workaround.patch - Bump to b85abacd902813daec5e44b97f275eb88caaf715, git192607. - On SLE15 and later, use make -Oline to synchronize configure output by lines Rev openSUSE:Factory/3 Md5 2f8fcc1bc35cc8558414a1b7ca7402b8 2022-05-10 13:09:46 dimstar_suse 975330
IMPORTANT: Please change gcc.spec.in and then run ./pre_checkin.sh! Do not change gcc.spec directly! Since GCC comes with a testsuite that runs for quite a long time and that test suite also contains some known failures, we should run the testsuite of GCC whenever the compiler is changed to ensure a high quality compiler. The package is now split into multiple parts, gcc$VER, gcc$VER-testresults and libffi$VER (plus various spec files for cross and icecream cross compilers). The testsuite is run from gcc$VER-testresults, a dummy package with the testresults, gcc$VER-testresults, is generated from it which contains testing logfiles and summary. Before checking in a new compiler, please do the following steps as QA measure to check that the new compiler does not introduce any new failures: - Run mbuild for all archs for at least the gcc$VER and the gcc$VER-testresults subpackages - When mbuild is finished, call /suse/rguenther/bin/compare-testresults.sh mbuild-directory (for the gcc$VER-testresults build). The output of that script should not show any failures. If it does, please fix them or discuss this with the gcc package maintainers. - Do not remove this file. Thanks, Your GCC packagers.