linux/poky.git/meta/recipes-devtools/gcc, branch styhead-5.1.4

classes/qemu: use tune to select QEMU_EXTRAOPTIONS, not package architecture

2025-01-29T14:20:43+00:00

Using the package architecture to select the right qemu options to pass to qemu-user is incorrect, and fails for recipes that set PACKAGE_ARCH to MACHINE_ARCH (as the qemuppc workarounds suggest) because there are not typically any options set for the machine name. Solve this by using TUNE_PKGARCH instead: for the majority of recipes this is the same value, but for machine-specific recipes it remains the same instead of changing to the machine name. This means we can remove the qemuppc workarounds, as they're obsolete. Also update the gcc-testsuite recipe which uses the same pattern to use TUNE_PKGARCH, and generalise the else codepath to avoid needing to update the list of architectures. [ YOCTO #15647 ] (From OE-Core rev: 6db23345fd653aa0b4e483d2635376dfe7bed3cd) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit 414b754a6cbb9cc354b1180efd5c3329568a2537) Signed-off-by: Steve Sakoman

gcc: Fix c++: tweak for Wrange-loop-construct

2025-01-09T14:02:48+00:00

This commit updates the warning to use a check for "trivially constructible" instead of "trivially copyable." The original check was incorrect, as "trivially copyable" only applies to types that can be copied trivially, whereas "trivially constructible" is the correct check for types that can be trivially default-constructed. This change ensures the warning is more accurate and aligns with the proper type traits. LLVM accepted a similar fix: https://github.com/llvm/llvm-project/issues/47355 PR c++/116731 [https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116731] (From OE-Core rev: b8260e5aca93a7000001013f8a950fb040141588) Signed-off-by: Marek Polacek Signed-off-by: Sunil Dora Signed-off-by: Steve Sakoman

gcc: add a backport patch to fix an issue with tzdata 2024b

2024-11-30T13:41:59+00:00

There is an issue in the std::chrono::tzdb parser that causes problems since the tzdata-2024b release started using %z in the main format. As a real world problem I encounter an issue with the waybar clock module, which ignores the timezone setting and only shows system time. (From OE-Core rev: 08dfd3849bd804f4760ebeca226645e65709a65a) Signed-off-by: Markus Volk Signed-off-by: Richard Purdie (cherry picked from commit 39018429f05511053ab12e23e7f4487ea25ee529) Signed-off-by: Steve Sakoman

libgfortran: fix buildpath QA issue

2024-11-26T13:37:09+00:00

The '-fdebug-prefix-map' options are used to map source files locations, otherwise, DW_AT_comp_dir will contain buildpath. The '-gno-record-gcc-switches' option is used to fix the buildpath introduced by '-fintrinsic-modules-path' option, which is automatically added by fortran. Here's some output from 'readelf --debug-dump libgfortran.so.5.0.0' when this option is not added: """ <0><1a37d3>: Abbrev Number: 4 (DW_TAG_compile_unit) <1a37d4> DW_AT_producer : (indirect string, offset: 0xd653): GNU Fortran2008 14.2.0 -m64 -march=core2 -mtune=core2 -msse3 -mfpmath=sse -mshstk -g -O2 -O2 -fstack-protector-strong -fimplicit-none -fno-repack-arrays -fno-underscoring -fcf-protection=full -fallow-leading-underscore -fbuilding-libgfortran -fPIC -fintrinsic-modules-path /ala-lpggp72/qichen/Yocto/builds/build-poky/tmp/work/ core2-64-poky-linux/libgfortran/14.2.0/recipe-sysroot-native/usr/bin/x86_64-poky-linux /../../lib/x86_64-poky-linux/gcc/x86_64-poky-linux/14.2.0/finclude -fpre-include=../../../../recipe-sysroot/usr/include/finclude/math-vector-fortran.h """ See https://gcc.gnu.org/pipermail/fortran/2024-October/061204.html for more detailed information. (From OE-Core rev: ba53108d33267b58306c6406ec90455bc221edaf) Signed-off-by: Chen Qi Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie (cherry picked from commit 1eb084956bcba83782bc2b24cf8cc89459a57e34) Signed-off-by: Steve Sakoman

gcc-source: Fix racing on building gcc-source-14.2.0 and lib32-gcc-source-14.2.0

2024-11-26T13:37:09+00:00

While enabling multilib, build gcc-source-14.2.0 and lib32-gcc-source-14.2.0 at the same time: $ MACHINE = "qemux86-64" $ require conf/multilib.conf $ MULTILIBS = "multilib:lib32" $ DEFAULTTUNE:virtclass-multilib-lib32 = "x86" $ bitbake gcc-source-14.2.0 lib32-gcc-source-14.2.0 ... $ cat tmp-glibc/work-shared/gcc-14.2.0-r0.vr2401/temp/log.task_order 20241012-064533.415426 do_recipe_qa (2688052): log.do_recipe_qa.2688052 20241012-064533.463783 do_recipe_qa (2688051): log.do_recipe_qa.2688051 20241012-064533.805164 do_fetch (2688257): log.do_fetch.2688257 20241012-064533.852955 do_fetch (2688256): log.do_fetch.2688256 20241012-064617.823714 do_unpack (2698542): log.do_unpack.2698542 20241012-064617.871730 do_unpack (2698541): log.do_unpack.2698541 ... There are two tasks for do_fetch, do_unpack and others, so there are race issues. Both of them have the same hardcode 'gcc' prefix in ${WORKDIR} and ${S}, explicitly disable lib32-gcc-source-14.2.0 for multilib Set gcc-source as BPN of gcc-source-14.2.0 (From OE-Core rev: 9609a7c9c6d809cc02480c3f12f8dd7c6f3fe9fc) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie (cherry picked from commit 901c47877e0710af50639f688e0bfdb851b762b5) Signed-off-by: Steve Sakoman

gcc: Fix spurious '/' in GLIBC_DYNAMIC_LINKER on microblaze

2024-09-05T20:48:47+00:00

(From OE-Core rev: f0eac82b9a1e4549b7d918df768c369ed7ab5183) Signed-off-by: Khem Raj Cc: Mark Hatle Signed-off-by: Richard Purdie

oeqa/selftest/gcc: Fix host key verfication failure

2024-08-13T08:29:15+00:00

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 Signed-off-by: Richard Purdie

gcc-runtime: enabling "network" task specific flag

2024-08-13T08:29:15+00:00

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 Signed-off-by: Richard Purdie

gcc: Upgrade to GCC 14.2

2024-08-08T11:04:39+00:00

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 Signed-off-by: Richard Purdie

gcc: unify cleanup of include-fixed, apply to cross-canadian

2024-08-03T06:56:10+00:00

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 Signed-off-by: Richard Purdie