summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc
Commit message (Collapse)AuthorAgeFilesLines
* oeqa/selftest/gcc: Fix host key verfication failureHarish Sadineni2024-08-131-1/+1
| | | | | | | | | | | | | | | | | | while runnig oe-selftest for gcc, testcases that need to be run on qemu are not running due to below failures. - Executing on ssh: mkdir -p /tmp/runtest.3549641 (timeout = 300) spawn [open ...] Host key verification failed. ERROR: Couldn't create remote directory /tmp/runtest.3549641 on ssh Host key verification failure is happening when ssh board config file name is defined as "ssh.exp" and there are multiple ssh.exp files generated during the build and a wrong ssh config was taken. To resolve this changed the board config file name to "linux-ssh.exp" which ensures correct ssh settings are used. (From OE-Core rev: d32ec0b4d242879ab8eaf96e1cb407e8f0bb9f3d) Signed-off-by: Harish Sadineni <Harish.Sadineni@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: enabling "network" task specific flagHarish Sadineni2024-08-131-0/+1
| | | | | | | | | | | | | | | Adding a "network" task specific flag which then triggers networking to be enabled for this task, it is otherwise disabled which will cause failures while running oe-selftest. Fixes the following issues while running oe-selftest for gcc: 1)ssh: connect to host X.X.X.X port 22: Network is unreachable. 2)Bad owner or permissions on /etc/ssh/ssh_config.d/50-redhat.conf. (From OE-Core rev: 35782416823fa863d26a338256f642f6bc480a96) Signed-off-by: Harish Sadineni <Harish.Sadineni@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to GCC 14.2Khem Raj2024-08-0837-143/+66
| | | | | | | | | | | | This is first bugfix release in GCC14 release series 100+ bugfixes [1] [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=14.2 (From OE-Core rev: 32b39de6a23f1e9ae5786d63f4c5849301eddbda) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: unify cleanup of include-fixed, apply to cross-canadianDenys Dmytriyenko2024-08-034-31/+8
| | | | | | | | | | | | | | | | | | | Since target and cross variants were already doing similar cleanup of include-fixed headers, as those aren't used, unify the code and also apply the same to cross-canadian variant. Some of those header files get processed with a tool that leaves absolute buildpaths inside the file's commented section, causing QA errors. Since those aren't used, let's remove them. This may be a temporary solution until the tool itself gets fixed to not embed absolute buildpaths in the header files: https://lists.openembedded.org/g/openembedded-core/topic/107268307 (From OE-Core rev: 9221e4ab8cca4c06dc3d5c1de2fd4ce46477578a) Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: remove paths to sysroot from configargs.h and checksum-options for ↵Oleksandr Hnatiuk2024-08-035-28/+29
| | | | | | | | | | | | | | | | | | gcc-cross-canadian Apply fixes from gcc-cross (84a78f46d594 and 0ead8cbdfb96) to gcc-cross-canadian. This will improve (but not fix) reproducibility of gcc-cross-canadian. Also move this code to functions to avoid code duplication. [RP: Tweak patch to make the function parameters clear and fix quoting issues ensuring the code exactly matches the original replacements with an additional parameter.] (From OE-Core rev: 350ff7d53f7506de2bc01f0efc569b8294b9afea) Signed-off-by: Oleksandr Hnatiuk <ohnatiuk@cisco.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tclibc-picolibc: Adds a new TCLIBC variant to build with picolibc as C libraryAlejandro Hernandez Samaniego2024-07-263-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enables usage of TCLIBC=picolibc extending OE functionality to build and use picolibc based toolchains to build baremetal applications. Picolibc is a set of standard C libraries, both libc and libm, designed for smaller embedded systems with limited ROM and RAM. Picolibc includes code from Newlib and AVR Libc, but adresses some of newlibs concerns, it retains newlibs directory structure, math, string and locale implementations, but removed the GPL bits used to build the library, swiches old C style code for C18 and replaces autotools with meson. This patch adds a picolibc recipe for the C library, a picolibc-helloworld recipe that contains an example application and a testcase that builds it. Picolibc can be built for ARM and RISCV architectures, its been tested both for 32 and 64 bits, the provided example recipe produces the following output: hello, world Runqemu does not automatically show any output since it hides QEMU stderr which is where the QEMU monitors output is directed to when using semihosting, but, manually running the same QEMU command does work properly. (From OE-Core rev: c7535ecaccb72ef21a61f9aec5c68e61fb4f6fb6) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-14: Mark CVE-2023-4039 as fixed in GCC14+Khem Raj2024-07-181-0/+1
| | | | | | | | (From OE-Core rev: 47b838eea7e3684d6b00bb7196313f0bfa519aba) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgfortran.inc: fix nativesdk-libgfortran dependenciesMartin Jansa2024-06-251-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * use virtual/* variables as INHIBIT_DEFAULT_DEPS does to avoid dependency on gcc-cross- from nativesdk-libgfortran * the dependency was added in: https://git.openembedded.org/openembedded-core/commit/?id=00fba52c8a6f6383137cf89fc7aa34cc3e2ff45f causing: build/oe-core $ bitbake -g nativesdk-libgfortran NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'gcc-cross-x86_64' (but virtual:nativesdk:/OE/build/oe-core/openembedded-core/meta/recipes-devtools/gcc/libgfortran_14.1.bb DEPENDS on or otherwise requires it). Close matches: gcc-cross-aarch64 ... with: MACHINE=qemuarm64 FORTRAN:forcevariable = ",fortran" * after: https://git.openembedded.org/openembedded-core/commit/?id=44fc7aa1468ff042739cc5a91c84ef5c2a09e0a3 nativesdk-libgfortran is pulled as dependency of nativesdk-gcc so this affects more people who didn't explicitly use nativesdk-libgfortran before * the INHIBIT_DEFAULT_DEPS and gcc-runtime was there since gcc-4.8: https://git.openembedded.org/openembedded-core/commit/?id=a5e7ee5770b9e0cf719c573efffd874440f74289 (From OE-Core rev: 5ce2e9c66cd2c08e141913ec65386f940353a8c5) Signed-off-by: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gfortran: update runtime dependenciesKai Kang2024-06-181-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | It fails to run both `gcc` and `gfortran` with errors: | root@qemux86-64:~# x86_64-poky-linux-gcc a.c | x86_64-poky-linux-gcc: fatal error: cannot execute 'as': posix_spawnp: No such file or directory then add binutils which provides `as` to RDEPENDS of gcc. libgfortran-dev provides libgfortran.spec which required by gfortran: | root@qemux86-64:~# gfortran hello.f95 | gfortran: fatal error: cannot read spec file 'libgfortran.spec': No such file or directory And gcc provides liblto_plugin.so: | root@qemux86-64:~# gfortran hello.f95 | gfortran: fatal error: '-fuse-linker-plugin', but liblto_plugin.so not found (From OE-Core rev: 44fc7aa1468ff042739cc5a91c84ef5c2a09e0a3) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: remove g77/f77Kai Kang2024-06-183-32/+2
| | | | | | | | | | | | | | | | | | | | | | | | g77/f77 has been removed from gcc 4.0.0 via commit: * b4117c30610 Makefile.def, [...]: Remove all mention of libf2c. When set FORTRAN = ",f77" it complains with error: | The following requested languages could not be built: f77 | Supported languages are: c,c,c++,fortran,go,lto,m2,objc,obj-c++ So remove g77/f77 from gcc recipes. [1]: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=b4117c30610 (From OE-Core rev: 6469c6a00066af24c87ec5dd7994ebbc610c3782) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix typo in increment expression in unicode from libstdc++Khem Raj2024-06-182-0/+77
| | | | | | | | | | This issue is seen when libstdc++ headers are used by clang18 see - https://github.com/llvm/llvm-project/issues/92586 (From OE-Core rev: 1506b779014b09ffd618b2e5d95aa00ff91d6f45) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Allow using libc++Dan McGregor2024-06-124-6/+3
| | | | | | | | | | | | | With the addition of the C++ runtime setting added recently, allow gcc to use libc++ as its runtime. There's some minor fixes still required, such as allowing setting the unwinder library. But this allows for testing libc++ with gcc. (From OE-Core rev: f84ae97e2bc081c972e78ee4a958f21111dbbfb6) Signed-off-by: Daniel McGregor <daniel.mcgregor@vecima.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: libgomp fix for gcc 14 warnings with mandb selftestRichard Purdie2024-05-211-1/+1
| | | | | | | | | | | ERROR: gcc-runtime-14.1.0-r0 do_package: QA Issue: gcc-runtime: Files/directories were installed but not shipped in any package: /usr/share/info /usr/share/info/libgomp.info-2 /usr/share/info/libgomp.info-1 (From OE-Core rev: 4f73ddd6c276dcd579d2113db1974d446dbf7751) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to GCC 14.1 releaseKhem Raj2024-05-2139-3481/+212
| | | | | | | | | | | | | | | | | | This is major release upgrade. major changes are listed in [1] and it has a list of bugs [2] fixed as well This release may differ in significant ways from prior gcc releases where it may require port the code to gcc 14, there is a porting guide [3] available. [1] https://gcc.gnu.org/gcc-14/changes.html [2] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=14.0 [3] https://gcc.gnu.org/gcc-14/porting_to.html (From OE-Core rev: fc48aa30e91ffe94f1012fe108fb1db5233a0bc0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Oe-selftest failure analysis - fix for vect-simd test failuresHarish Sadineni2024-03-232-0/+27
| | | | | | | | | | | | | | | In gcc vect module, the vect-simd-clone-10.c & vect-simd-clone-12.c tests are failed with below error, due to a bug in testcase: xgcc: fatal error: cannot specify '-o' with '-c', '-S' or '-E' with multiple files compilation terminated' Detailed bug info & upstream fix is here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113899 Upstream Status: Backport [https://gcc.gnu.org/g:948dbc5ee45f9ffd5f41fd6782704081cc7c8c27] (From OE-Core rev: 50b6b938ec91dee346642b95cdcb35043be1697c) Signed-off-by: Harish Sadineni <Harish.Sadineni@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Oe-selftest failure analysis - fix for tcl errorsHarish Sadineni2024-03-181-2/+2
| | | | | | | | | | | | | | gcc testsuite unable to read the value of variable $do-what-limit and causing below tcl errors. ERROR: can't read "do": no such variable while executing "set do_what $do-what-limit" To fix this, quote the variable using braces, as in ${do-what-limit}. (From OE-Core rev: e59421468d96282057f5176438a76a325b987e47) Signed-off-by: Harish Sadineni <Harish.Sadineni@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Move gdb pretty printer file to auto-load locationKhem Raj2024-02-091-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | When debugging a C++ program on target using libcstdc++, gdb does not find the pretty printer python support, this is because the init file is installed into /usr/lib which is excluded from gdb's default list of directories to load config's from, where as defaults to load from datadir is still on, it therefore does not load this file warning: File "/usr/lib/libstdc++.so.6.0.33-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". This leaves the libstdc++ pretty-printers disabled even though added via IMAGE_INSTALL += "gcc-runtime-dbg" Comment on adding missing runtime dependency on datetime python module for the pretty printer to work/load successfully. Once the pretty-printer gdb file is moved out of libdir, it may become empty therefore delete it if its empty. (From OE-Core rev: d24e16d192f21aa68b5274496efaba1d913f37c2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Update status of CVE-2023-4039Simone Weiß2024-01-261-0/+1
| | | | | | | | | | | | This is fixed via a patch added in gcc-13.2.inc already, but still reported e.g. for libgcc as it is not defining an own source but use the shared gcc-source. (From OE-Core rev: 301d45eacfd4ae6bddfb13207e2af9e8b4662bc8) Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: depend on zstdSean Nyekjaer2023-09-291-1/+1
| | | | | | | | | | | | | | | | | | | | Add zstd LTO support for target and nativesdk compiler. This also brings gcc into sync with gcc-cross. % x86_64-oe-linux-gcc -v [...] Supported LTO compression algorithms: zlib zstd gcc version 12.2.0 (GCC) % x86_64-oesdk-linux-gcc -v [...] Supported LTO compression algorithms: zlib gcc version 12.2.0 (GCC) (From OE-Core rev: 2f6e3d32ad73ef8e0e3d3b89702d85c36358c00c) Signed-off-by: Sean Nyekjaer <sean@geanix.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: backport a fix for ICE caused by CVE-2023-4039.patchMartin Jansa2023-09-203-71/+197
| | | | | | | | | | | | | | * see: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111418 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111411 * add git headers to 0025-gcc-testsuite-mips.patch so that it does easily apply with other patches with git am (From OE-Core rev: 760068c5868380b0e833155020365735f55314c3) Signed-off-by: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix -fstack-protector issue on aarch64Ross Burton2023-09-132-0/+3094
| | | | | | | | | | | | | | | | This series of patches fixes deficiencies in GCC's -fstack-protector implementation for AArch64 when using dynamically allocated stack space. This is CVE-2023-4039. See: https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64 https://github.com/metaredteam/external-disclosures/security/advisories/GHSA-x7ch-h5rf-w2mf for more details. (From OE-Core rev: 750396ca55e9f165a77dc94f841a953b9a6520d5) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fresh 0003-64-bit-multilib-hack.patch to add loongarch64 supportZang Ruochen2023-09-091-1/+53
| | | | | | | | (From OE-Core rev: 1a209ef31165049c450018c7722013aa4d983fd8) Signed-off-by: Zang Ruochen <zangruochen@loongson.cn> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-sanitizers: Add loongarch as a compatible architecture.Zang Ruochen2023-09-071-2/+2
| | | | | | | | | https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=600413c4f3d70392285192fb99634bcbeb97f83f (From OE-Core rev: 50649aa576b161751fd9b11ed98fe4a26b0781f8) Signed-off-by: Zang Ruochen <zangruochen@loongson.cn> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: remove bashismPeter Marko2023-09-031-1/+1
| | | | | | | | | | | | | | Debian 12 no longer supports replacing dash with bash as default shell. Therefore to achieve compatibility with Debian 12, all bashisms need to be removed. Shell comparison via == gives an error with dash and thus the condition is always false. (From OE-Core rev: 3723b26f82219ff71823335d550dbf29086d63d4) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Add patch to improve testsuite failures, particularly mipsRichard Purdie2023-08-152-0/+226
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Disable loongson-mmi runtine, qemu doesn't appear to fully support them even if some of the instruction decoding is there. Also disable MSA mips runtime extensions. For some reason qemu appears to accept the test code when it shouldn't. Our selected MIPS cpu for QEMU doesn't support them. MIPS is unusual in the gcc testsuite as it uses EFFECTIVE_TARGETS and loops multiple times through the vector testsuite. In the case of the two above, we can compile/link them but not run them. Even with the runtime disabled, if the code marks it as a runtime test, it will elevate itself to that. Setting the default target to compile therefore isn't enough. Therefore add code to downgrade runtime tests to link tests if the hardware support isn't there to run them. This avoids thousands of test failures. To do this we have to hook downgrade code into the main test runner. Enable that downgrading for other cases where hardware to run vector extensions is unavailable to remove test failures on other architectures too. Also, for gcc.target tests, add checks on wheter loongson or msa code can be run before trying that, allowing downgrading of tests there to work too. Parts of the patch may be able to be split off and acceptable to upstream with discussion. Need to investigate why qemu-user passes the 'bad' instructions'. For now, this should at least remove hundreds of test failures and improve test failures on non-mips too now a root cause of some was identified. (From OE-Core rev: bdb744edfec77d3fb000da0fe432689089b20d02) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-testsuite: Set qemu options for mips correctlyRichard Purdie2023-08-151-2/+6
| | | | | | | | | MIPS sets QEMU CPU values similarly to ppc and doens't support 'max'. Allow this to filter through correctly to the toolchain testing. (From OE-Core rev: 8c939780228d1440190a87cc24abd72d26aade74) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-testsuite: Fix qemu binary filtering code logic errorRichard Purdie2023-08-151-2/+2
| | | | | | | | | | This code doesn't do what it first might appear to, it would for example remove 'm' characters from the left side of qemu-mips leaving 'ips'. Fix it to stop anyone else being confused by the subtle logic error. (From OE-Core rev: 888a7edf1c611eaf99eaf10a072ecc82cb386735) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-crosssdk: ignore MULTILIB_VARIANTS in signature computationChen Qi2023-08-101-0/+2
| | | | | | | | | | | | | | | | | | | The gcc_multilib_setup function is a function that is run at the do_configure step, so it's counted into the signature computation. The MULTILIB_VARIANTS this function uses is also extracted to be taken into consideration. After the change of setting MULTILIB_VARIANTS explictly vardeps on MULTILIBS, the change of MULTILIBS changes the signature, thus causing rebuilding. However, in case of gcc-crosssdk, the setting of multilib should have no effect on it, as it's used to build nativesdk packages, not the target packages. So ignore MULTILIB_VARIANTS in signature computation. This fixes oe-selftest case sstatetests.SStateHashSameSigs2.test_sstate_nativesdk_samesigs_multilib. (From OE-Core rev: 537c71162a711dec32a63a657c4b101269a3e267) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to 13.2 releaseKhem Raj2023-07-3035-63/+100
| | | | | | | | | | | | This is a bugfix [1] release on GCC-13 release with 58 [2] bugs fixed [1] https://gcc.gnu.org/pipermail/gcc-announce/2023/000179.html [2] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&list_id=390723&resolution=FIXED&target_milestone=13.2 (From OE-Core rev: 89175021995db0e7f81a74c6bafcebdce9de8939) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve_check: convert CVE_CHECK_IGNORE to CVE_STATUSAndrej Valek2023-07-211-2/+1
| | | | | | | | | | | | | - Try to add convert and apply statuses for old CVEs - Drop some obsolete ignores, while they are not relevant for current version (From OE-Core rev: 1634ed4048cf56788cd5c2c1bdc979b70afcdcd7) Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Reviewed-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-testsuite: Fix ppc cpu specificationRichard Purdie2023-07-181-2/+3
| | | | | | | | | | | | | | | After this change in qemu: https://gitlab.com/qemu-project/qemu/-/commit/c7e89de13224c1e6409152602ac760ac91f606b4 there is no 'max' cpu model on ppc. Drop it to clean up ppc gcc testsuite failures. In order for this to work we do need to pull in the alternative cpu option from QEMU_EXTRAOPTIONS on powerpc. (From OE-Core rev: c447f2b21b20fb2b1829d540af2cc0bf8242700c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: don't pass --enable-standard-branch-protectionRoss Burton2023-07-141-1/+0
| | | | | | | | | | | | | | | | | | | | By changing the default code generation of GCC we're inadvertently breaking the GCC test suite, which has ~120K+ more failures when run for aarch64 compared to x86-64. This was because the generated code fragments included the BTI instructions, which the test case wasn't expecting. We can't tell the tests globally to run without branch protection, as that will break the tests which also turn it on. Remove the enabling of branch protection by standard in GCC, we'll enable it in the tune files instead. (From OE-Core rev: bb4b9017db6a893ed054a2d2ad4cc671dec09c42) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcc: Always use BFD linkerKhem Raj2023-06-131-0/+2
| | | | | | | | | | | libgcc is linked with GNU BFD linker make sure it does not assume default ld to be BFD linker rather demand it explicitly (From OE-Core rev: 856b4ec58fd5391069eaf43ab1b7426d49d9b7de) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to 13.1.1Khem Raj2023-05-282-59/+23
| | | | | | | | | | | | | | | | | Some distros e.g. gentoo have latest on gcc-13 branch and we have a situation where libstdc++ ABI is changed between 13.1 and 13.2 so official 13.1 release based uninative will no longer work on these distros, therefore switch to a snapshot that includes [1] which fixes it [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108969 Reported-by: Martin Jansa <Martin.Jansa@gmail.com> (From OE-Core rev: d554c404166f6ba1aa247c377fa9d3316e53aa40) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to GCC 13.1 releaseKhem Raj2023-05-2639-421/+336
| | | | | | | | | | | | | | | | | | | - Package libhwasan_preinit.o, its available on some arches e.g. x86_64 on gcc13+ - GCC 13 Porting guide [1] and major changes [2] and detailed documentation [3] - Fix aarch64 cross build when S != B [1] https://www.gnu.org/software/gcc/gcc-13/porting_to.html [2] https://www.gnu.org/software/gcc/gcc-13/changes.html [3] https://gcc.gnu.org/onlinedocs/13.1.0/ (From OE-Core rev: b80c020eaeaaae82e5b32209ca8608b36eaaee40) (From OE-Core rev: bea46612fd9106cc5b46eb1d81623b6492563c13) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc/go: Drop crosssdk suffix from virtual provides to improve dependency ↵Richard Purdie2023-05-023-4/+3
| | | | | | | | | | | | | | | handling There is little point in having "crosssdk" suffex added to the virtual provider within gcc/go since the TARGET_PREFIX or SDK_PREFIX already encapsulates this. Remove it allowing some of the special case overriding to be removed. This also allows removal of some of the MLPREFIX usage since again, the triplet also covers this. (From OE-Core rev: fe0206ba482d209b24e636d578aa68ba5e67ba1b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Drop crosssdk suffix from virtual provides to improve dependency ↵Richard Purdie2023-05-022-2/+2
| | | | | | | | | | | | handling There is little point in having "crosssdk" suffex added to the virtual provider within binutils since the TARGET_PREFIX or SDK_PREFIX already encapsulates this. Remove it allowing some of the special case overriding to be removed. (From OE-Core rev: 6856fc5c848cc2564bebe03a007ef109f46d0adb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-shared-source: do not use ${S}/.. in deploy_source_date_epochPeter Marko2023-03-251-2/+2
| | | | | | | | | | | | | | | | | | | | This function is referencing '${S}/..'. It uses ${S} only as good known directory path to start traversing from, and it does not need it to exist or be populated. If ${S} does not exist yet, the function will fail because it cannot evaluate path .. from non-existing directory. Reproducer (verified in master and kirkstone): bitbake gcc -c deploy_source_date_epoch bitbake gcc -c cleansstate rm -rf build/tmp bitbake gcc -c deploy_source_date_epoch (From OE-Core rev: 42661a59cda164b2d236ffc35b4d8cf43312b677) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: add support for loongarch64Jialing Zhang2023-03-231-0/+1
| | | | | | | | | | | glibc gcc vulkan add support for loongarch64 (From OE-Core rev: 526b9a8ebacf07690dfc5beb1788ab7a5bef8423) Signed-off-by: Jialing Zhang <zhangjialing@loongson.cn> Signed-off-by: Qizheng Zhu <zhuqizheng@loongson.cn> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-source: Ensure deploy_source_date_epoch sstate hash doesn't changeRichard Purdie2022-11-071-0/+7
| | | | | | | | | | | | | | | | Currently if you switch machines, gcc-source do_deploy_source_date_epoch would re-run as the stamps are tune specific. This hasn't caused much of an issue until now, however if we fix the gcc recipes to reuse the timestamp from this task, it does then create problems. Copy code from allarch to ensure this task hash doesn't change between machines/tunes. (From OE-Core rev: 7e052d03464ba5e880a6c5a0e45ff2f467ef97e8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-source: Drop gengtype manipulationRichard Purdie2022-11-071-2/+0
| | | | | | | | | | | | | | Whilst we patch gengtype.cc, we don't patch gengtype-lex.cc which would be the file which would trigger regeneration of files. The real bug that was likely the cause for this fix is probably SDE issues with gcc shared workdir so this code can now be dropped. (From OE-Core rev: 7ab82b5db2a737c2a0266280b15d343a27c0e1d5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-source: Fix gengtypes raceRichard Purdie2022-11-071-1/+1
| | | | | | | | | | | | | | | | | | gcc renamed .c files to .cc files: https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=5c69acb32329d49e58c26fa41ae74229a52b9106 but we didn't fix this reference which meant we re-introduced a race around gengtypes-lex.c. This lead to the race reappearing on the autobuilder. Fix the naming to avoid the problem again. [YOCTO #14953] (From OE-Core rev: dbca40ed399405b663dbc3894e35596a2615f47d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-shared-source: Fix source date epoch handlingRichard Purdie2022-11-071-0/+10
| | | | | | | | | | | | | | | | | | | | | The source date epoch for gcc isn't being transferred from the shared workdir to the current WORKDIR for the specific recipe. This results in the clamping code within sstate.bbclass using a value from 2011 which changes the timestamps of many files. Since this happens part way through the build, if pieces of gcc haven't built, or build/rebuild later, we see things rebuilding when they should not and for generated files, races are possible. Fix this by copying the SDE from the shared workdir into the recipe workdir. [YOCTO #14953] (From OE-Core rev: b996293b4c8ab7ff3ed852045d17290df29205df) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Allow -Wno-error=poison-system-directories to take effectPeter Kjellerstedt2022-10-251-18/+18
| | | | | | | | | | | | The change in commit e903b29f (gcc-cross: pass -Werror=poison-system-directories to compiler stages) made it impossible to disable the error using -Wno-error=poison-system-directories. (From OE-Core rev: 1cb0245539f7d5277fae4e9abc7f2a0130d0caa8) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: set the default target archDaniel McGregor2022-09-292-1/+11
| | | | | | | | | | | | | | | | The default x86-64 architecture for target gcc (ie, the one in poky build appliances) is native. Since we have a variety of build systems it will occasionally produce instructions that don't work on all of our development system. Instead, set gcc's default architecture to the one specified in TUNE_CC_ARCH, that guarantees that gcc-runtime and any binaries produced are compatible with the target machine type. (From OE-Core rev: 52b952e474e655f8b4b6501813d57e20c9f02ba2) Signed-off-by: Daniel McGregor <daniel.mcgregor@vecima.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: add default plugin linkerSamuli Piippo2022-09-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix multilib sdk issue where gcc is unable to find linker. Previous fix was in cdd86896c8d29135f937968e9aa07f919cf543d3 using real-ld symlink, but that prevented switching between bfd and gold linkers. Running compiler with debug arguments shows that collect2 tries and fails to find linker using the multilib triples: $ $CC -v -Wl,-debug ... Looking for 'real-ld' Looking for 'collect-ld' Looking for 'mips-oemllib32-linux-ld' Looking for 'mips-oe-linux-mips-oemllib32-linux-ld' ... collect2 version 12.2.0 ld_file_name = not found ... collect2: fatal error: cannot find ‘ld’ Using --with-plugin-ld=ld in gcc-cross-canadian builds to set default linker name for collect2, lets it find the linker correctly: Looking for 'real-ld' Looking for 'collect-ld' Looking for 'ld' ... collect2 version 12.2.0 ld_file_name = /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/libexec/mips-oe-linux/gcc/mips-oe-linux/12.2.0/ld Swith between bfd and gold linker works as expected now: $ $CC -v -Wl,-debug -fuse-ld=gold ... Looking for 'real-ld' Looking for 'collect-ld' Looking for 'ld.gold' ... collect2 version 12.2.0 ld_file_name = /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/libexec/i686-oe-linux/gcc/i686-oe-linux/12.2.0/ld.gold (From OE-Core rev: cf1bb16b7f9f81514feaf1e4ecffd9039387bb89) Signed-off-by: Samuli Piippo <samuli.piippo@qt.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "gcc-cross-canadian: Add symlink to real-ld alongside other symlinks"Samuli Piippo2022-09-171-2/+0
| | | | | | | | | | | | This reverts commit cdd86896c8d29135f937968e9aa07f919cf543d3. real-ld is always used if that is found, which means you cannot switch between bfd and gold linkers using -fuse-ld gcc option. (From OE-Core rev: 53ae417c63a4a7ff4a729d3653a31cf1c0758f10) Signed-off-by: Samuli Piippo <samuli.piippo@qt.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: remove obsolete MinGW patchRoss Burton2022-09-092-27/+0
| | | | | | | | | | | | | | This patch appears to be obsoleted by 217d5be, in GCC 11.1 onwards. libstdc++: Test errno macros directly for all targets [PR 93151] This applies the same changes to the djgpp and mingw versions of error_constants.h as r11-6137 did for the generic version. (From OE-Core rev: e3157da1408b4e6281fdf28825b79c266e93c05e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: remove obsolete poisoned calloc workaroundRoss Burton2022-09-092-57/+0
| | | | | | | | | This was fixed upstream in de6f402a, as part of 12.2. (From OE-Core rev: d5e6768f30579abc8559aab60429a292a4c49f3d) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: remove obsolete 0012-export-CPP.patchRoss Burton2022-09-072-51/+0
| | | | | | | | | | This patch is no longer needed, the upstream Makefile exports CPP from CPP_FOR_BUILD since 12.1. (From OE-Core rev: c7546939574dc5e976caae8f0e705b805962ff03) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-01-10 03:43:55 +0000