Hello Randy,

On 16-06-2022 19:49, Randy MacLeod wrote:
On 2022-06-15 22:19, Sundeep KOKKONDA wrote:
Hello,

GCC regression test performed on /Kirkstone/ with gcc-11.3 & gcc-11.2. The results are *NOT* identical. Below is test summary.

*gcc-11.3:*
/                === gcc Summary ===/
/# of expected passes            126552/
/# of unexpected failures        24295/
/# of unexpected successes       77/
/# of expected failures          782/
/# of unresolved testcases       10/
/# of unsupported tests          2760/
//home/bft1/skokkonda/kirkstone/poky/build/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc version 11.3.0 (GCC)/

*gcc-11.2:*
/                === gcc Summary ===/
/# of expected passes            125933/
/# of unexpected failures        24215/
/# of unexpected successes       76/
/# of expected failures          773/
/# of unresolved testcases       10/
/# of unsupported tests          2779/
//home/bft1/skokkonda/kirkstone-gcc-11.2/poky/build/sdk/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc version 11.2.0 (GCC)


/

/11.3: # of expected passes            126552/
//11.2: # of expected passes            125933//

So >= 619 additional tests were added and they mostly pass (as you'd expect).
That's good news.


/11.3: # of unexpected failures        24295/
/11.2: # of unexpected failures        24215/
/
/
/So 80 additional unexpected failures - can you summarize what these failures are?
/
There are 83 tests failed with GCC-11.3 and out of them most of the failed cases (75 tests) are /execution /tests and the remaining are /test for excess errors/ (Tests with excess messages output to stderr). The Failed tests list is attached.
/Were any of them fixed after the 11.3 tag?
/
Does it mean, do you want me to test on 11.4 and compare?
/
Are they related to one part of the toolchain or spread across various features?
Are they reproducible when buiding outside of bitbake?/
The test failures are from gcc.dg/torture, gcc.c-torture & gcc.target testsuites.
/
/
/The other differences are less significant.
If you post similar data in future emails, please do the math for people!
/
/
/
//
gcc-11.3 & gcc-11.2 test summaries are attached.

I didn't look at these yet but  thanks for providing them.

Since we're not seeing any runtime regression in our Yocto
test suite, I suspect that we shouldn't panic but should instead
just work to understand, fix, upstream and monitor for future regressions.

../Randy



--
Thanks,
Sundeep K.




--
# Randy MacLeod
# Wind River Linux

FAIL: gcc.c-torture/execute/bitfld-10.c   -O0  execution test
FAIL: gcc.c-torture/execute/bitfld-10.c   -O1  execution test
FAIL: gcc.c-torture/execute/bitfld-10.c   -O2  execution test
FAIL: gcc.c-torture/execute/bitfld-10.c   -O3 -g  execution test
FAIL: gcc.c-torture/execute/bitfld-10.c   -Os  execution test
FAIL: gcc.c-torture/execute/bitfld-10.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
FAIL: gcc.c-torture/execute/bitfld-10.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
FAIL: gcc.c-torture/execute/pr103052.c   -O0  execution test
FAIL: gcc.c-torture/execute/pr103052.c   -O1  execution test
FAIL: gcc.c-torture/execute/pr103052.c   -O2  execution test
FAIL: gcc.c-torture/execute/pr103052.c   -O3 -g  execution test
FAIL: gcc.c-torture/execute/pr103052.c   -Os  execution test
FAIL: gcc.c-torture/execute/pr103052.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
FAIL: gcc.c-torture/execute/pr103052.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
FAIL: gcc.c-torture/execute/pr103255.c   -O0  execution test
FAIL: gcc.c-torture/execute/pr103255.c   -O1  execution test
FAIL: gcc.c-torture/execute/pr103255.c   -O2  execution test
FAIL: gcc.c-torture/execute/pr103255.c   -O3 -fomit-frame-pointer 
-funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
FAIL: gcc.c-torture/execute/pr103255.c   -O3 -g  execution test
FAIL: gcc.c-torture/execute/pr103255.c   -Os  execution test
FAIL: gcc.c-torture/execute/pr103255.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
FAIL: gcc.c-torture/execute/pr103255.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
FAIL: gcc.c-torture/execute/pr104814.c   -O0  execution test
FAIL: gcc.c-torture/execute/pr104814.c   -O1  execution test
FAIL: gcc.c-torture/execute/pr104814.c   -O2  execution test
FAIL: gcc.c-torture/execute/pr104814.c   -O3 -fomit-frame-pointer 
-funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
FAIL: gcc.c-torture/execute/pr104814.c   -O3 -g  execution test
FAIL: gcc.c-torture/execute/pr104814.c   -Os  execution test
FAIL: gcc.c-torture/execute/pr104814.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
FAIL: gcc.c-torture/execute/pr104814.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
FAIL: gcc.dg/analyzer/data-model-1.c  (test for warnings, line 254)
FAIL: gcc.dg/analyzer/strndup-1.c  (test for warnings, line 11)
FAIL: c-c++-common/cpp/pr104147.c  -Wc++-compat  execution test
FAIL: gcc.dg/pr102224.c execution test
FAIL: gcc.dg/pr102798.c execution test
FAIL: gcc.dg/pr103860.c execution test
FAIL: gcc.dg/sso-16.c execution test
FAIL: gcc.dg/ipa/pr103083-1.c execution test
FAIL: gcc.dg/lto/pr101868 c_lto_pr101868_0.o-c_lto_pr101868_3.o execute -O2 
-fno-strict-aliasing -flto
FAIL: gcc.dg/lto/pr101949 c_lto_pr101949_0.o-c_lto_pr101949_1.o execute -O2 
-fipa-pta -flto -flto-partition=1to1
FAIL: gcc.dg/torture/pr102139.c   -O0  execution test
FAIL: gcc.dg/torture/pr102139.c   -O1  execution test
FAIL: gcc.dg/torture/pr102139.c   -O2  execution test
FAIL: gcc.dg/torture/pr102139.c   -O3 -g  execution test
FAIL: gcc.dg/torture/pr102139.c   -Os  execution test
FAIL: gcc.dg/torture/pr102139.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
FAIL: gcc.dg/torture/pr102139.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
FAIL: gcc.dg/torture/pr103181.c   -O0  execution test
FAIL: gcc.dg/torture/pr103181.c   -O1  execution test
FAIL: gcc.dg/torture/pr103181.c   -O2  execution test
FAIL: gcc.dg/torture/pr103181.c   -O3 -g  execution test
FAIL: gcc.dg/torture/pr103181.c   -Os  execution test
FAIL: gcc.dg/torture/pr103181.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
FAIL: gcc.dg/torture/pr103181.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
FAIL: gcc.dg/torture/pr103237.c   -O0  execution test
FAIL: gcc.dg/torture/pr103237.c   -O1  execution test
FAIL: gcc.dg/torture/pr103237.c   -O2  execution test
FAIL: gcc.dg/torture/pr103237.c   -O3 -fomit-frame-pointer -funroll-loops 
-fpeel-loops -ftracer -finline-functions  execution test
FAIL: gcc.dg/torture/pr103237.c   -O3 -g  execution test
FAIL: gcc.dg/torture/pr103237.c   -Os  execution test
FAIL: gcc.dg/torture/pr103237.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
FAIL: gcc.dg/torture/pr103237.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
FAIL: gcc.dg/torture/pr105198.c   -O0  execution test
FAIL: gcc.dg/torture/pr105198.c   -O1  execution test
FAIL: gcc.dg/torture/pr105198.c   -O2  execution test
FAIL: gcc.dg/torture/pr105198.c   -O3 -fomit-frame-pointer -funroll-loops 
-fpeel-loops -ftracer -finline-functions  execution test
FAIL: gcc.dg/torture/pr105198.c   -O3 -g  execution test
FAIL: gcc.dg/torture/pr105198.c   -Os  execution test
FAIL: gcc.dg/torture/pr105198.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
FAIL: gcc.dg/torture/pr105198.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
FAIL: gcc.dg/vect/bb-slp-pr101615-2.c execution test
FAIL: gcc.dg/vect/bb-slp-pr101615-2.c -flto -ffat-lto-objects execution test
FAIL: gcc.target/i386/avx-pr102224.c execution test
FAIL: gcc.target/i386/avx512f-pr101471.c (test for excess errors)
FAIL: gcc.target/i386/avx512f-pr101471.c execution test
FAIL: gcc.target/i386/pr102498.c execution test
FAIL: gcc.target/i386/pr102627.c execution test
FAIL: gcc.target/i386/pr104971.c execution test
FAIL: gcc.target/i386/pr105000-1.c (test for excess errors)
FAIL: gcc.target/i386/pr105000-2.c (test for excess errors)
FAIL: gcc.target/i386/pr105000-3.c (test for excess errors)
FAIL: gcc.target/i386/pr99754-1.c execution test
FAIL: gcc.target/i386/pr99754-2.c execution test
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#167079): 
https://lists.openembedded.org/g/openembedded-core/message/167079
Mute This Topic: https://lists.openembedded.org/mt/91503792/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to