Dear contributor,

Our automatic CI has detected problems related to your patch(es). Please find 
some details below.

In  arm-eabi thumb v8-a hard, after:
  | commit gcc-17-178-g167f5e2d229
  | Author: Tomás Ortín Fernández <[email protected]>
  | Date:   Fri Mar 20 15:57:13 2026 +0100
  | 
  |     analyzer: model mktemp-family success/failure outcomes [PR105890]
  |     
  |     The known_function handlers for the mktemp family all use
  |     set_any_lhs_with_defaults, leaving the return value unconstrained.
  |     This means the analyzer cannot distinguish the success path from the
  | ... 66 lines of the commit log omitted.

Produces 4 regressions 4 fixes:
  | 
  | regressions.sum:
  | Running gcc:gcc.dg/analyzer/analyzer.exp ...
  | FAIL: gcc.dg/analyzer/mkostemp-1.c (test for warnings, line 108)
  | FAIL: gcc.dg/analyzer/mkostemp-1.c (test for warnings, line 114)
  | FAIL: gcc.dg/analyzer/mkostemps-1.c (test for warnings, line 114)
  | FAIL: gcc.dg/analyzer/mkostemps-1.c (test for warnings, line 120)
  | 
  | fixes.sum:
  | Running gcc:gcc.dg/analyzer/analyzer.exp ...
  | FAIL: gcc.dg/analyzer/mkostemp-1.c (test for warnings, line 113)
  | FAIL: gcc.dg/analyzer/mkostemp-1.c (test for warnings, line 107)
  | FAIL: gcc.dg/analyzer/mkostemps-1.c (test for warnings, line 113)
  | FAIL: gcc.dg/analyzer/mkostemps-1.c (test for warnings, line 119)

Used configuration :
 *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-a+simd 
-mfpu=auto -mfloat-abi=hard
 *configure and test flags:* --target arm-eabi --disable-multilib 
--with-mode=thumb --with-arch=armv8-a+simd --with-fpu=crypto-neon-fp-armv8 
--with-float=hard 
--target_board=-mthumb/-march=armv8-a+simd/-mfpu=auto/-mfloat-abi=hard 
qemu_cpu=any

We track this bug report under https://linaro.atlassian.net/browse/GNU-1888. 
Please let us know if you have a fix.

If you have any questions regarding this report, please ask on 
[email protected] mailing list.

-----------------8<--------------------------8<--------------------------8<--------------------------

The information below contains the details of the failures, and the ways to 
reproduce a debug environment:

You can find the failure logs in *.log.1.xz files in
 * 
http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_hard_eabi-build/builds/10047/archive/artifacts/00-sumfiles/
The full lists of regressions and improvements as well as configure and make 
commands are in
 * 
http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_hard_eabi-build/builds/10047/archive/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
 * 
http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_hard_eabi-build/builds/10047/archive/artifacts/sumfiles/xfails.xfail

Current build   : 
http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_hard_eabi-build/builds/10047/archive/artifacts/
Reference build : 
http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_hard_eabi-build/builds/10045/archive/artifacts/

Instruction to reproduce the build : 
https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1/167f5e2d22970daf1160acd872cd4d5de63a96b4/tcwg_gnu_embed_check_gcc/master-thumb_v8a_hard_eabi/reproduction_instructions.txt

Full commit : See in git+ssh://[email protected]/git/gcc.git

Reply via email to