| Summary: | Investigate GCC Wstringop-overflow failures | ||
|---|---|---|---|
| Product: | [QA/Testing] Functional (self) Testing | Reporter: | Ross Burton <ross.burton> |
| Component: | oe-selftest | Assignee: | Harish Sadineni <Harish.Sadineni> |
| Status: | ACCEPTED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | sundeep.kokkonda, tim.orling |
| Version: | 6.1 | ||
| Target Milestone: | 6.2 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
Also:
ptestresult.gcc-user.c-c++-common/Wstringop-overflow-2.c -Wc++-compat (test for warnings, line 103)
The full report at https://valkyrie.yocto.io/pub/releases/yocto-6.1_M1.rc1/testreport.txt lists each of the failures and the corresponding lines.
These are known GCC upstream testsuite failures, tracked in GCC bugzila https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124619. These failures are not specific to Yocto or qemuarm. Work is ongoing in gcc upstream. Patches were under review in gcc patches mailing list. https://inbox.sourceware.org/gcc-patches/bmm.hnksol2j0g.gcc.gcc.rearnsha.215.612.REVIEW@forge-stage.sourceware.org/ |
The gcc test suite when run under qemuarm has a large number of failures in the following tests: testseries | result_id : qemuarm-tc | oeselftest_debian-12_qemuarm_20260610100141 ptestresult.gcc-g++-user.c-c++-common/Wstringop-overflow-2.c -std=gnu++98 (test for warnings, line 55) ptestresult.gcc-g++-user.g++.dg/warn/Wstringop-overflow-3.C -std=gnu++20 (test for warnings, line 105) There's probably a single root cause which should be investigated to remove 140 failures from the test report.