[Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64

2025-06-18 Thread ci_notify--- via Gcc-regression
Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-aarch64, after: | commit gcc-16-1550-g9244ea4bf556 | Author: Andrew MacLeod | Date: Mon Jun 16 15:41:47 2025 -0400 | | Snap subrange boundries to bitma

Regressions on native/master at commit r16-1566 vs commit r16-1560 on Linux/x86_64

2025-06-18 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r16-1566 vs commit r16-1560 on Linux/x86_64 New failures: New passes: FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 execution test FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 execution test

Regressions on master at commit r16-1565 vs commit r16-1559 on Linux/x86_64

2025-06-18 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r16-1565 vs commit r16-1559 on Linux/x86_64 New failures: FAIL: 30_threads/async/async.cc -std=gnu++17 execution test New passes: FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 execution test FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 executio

Regressions on master at commit r16-1567 vs commit r16-1565 on Linux/x86_64

2025-06-18 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r16-1567 vs commit r16-1565 on Linux/x86_64 New failures: New passes: FAIL: 30_threads/async/async.cc -std=gnu++17 execution test

Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64

2025-06-18 Thread Sam James via Gcc-regression
Could you file a glibc bug for this please? It needs some analysis to see if it's an FP or not. There's actually a suppression for -Os already there: if (elem < table_size) { /* Compare the byte sequence but