[Linaro-TCWG-CI] gcc-16-6458-g1e314be3ccc: Failure on aarch64

ci_notify--- via Gcc-regression <[email protected]>
Newsgroups gmane.comp.gcc.regression
Message-ID <[email protected]>
Dear contributor,

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

In bootstrap_build master-aarch64-bootstrap_profiled_lto, after:
  | commit gcc-16-6458-g1e314be3ccc
  | Author: Kugan Vivekanandarajah <[email protected]>
  | Date:   Fri Jan 2 07:58:28 2026 +1100
  | 
  |     [PATCH] [AutoFDO/devirt] Fix ICE with duplicate speculative ID
  |     
  |     This happens due to autoprofile pass makes edge make_speculative.
  |     Then ipa-devirt does the same with the same speculative_id which
  |     reults in duplicate speculative_id and ICE.
  | ... 31 lines of the commit log omitted.

Produces Failure:
  | Results changed to
  | # reset_artifacts:
  | -10
  | # true:
  | 0
  | # build_abe bootstrap_profiled_lto:
  | # FAILED
  | # First few build errors in logs:
  | # 01:59:49     test.i:31:1: internal compiler error: verify_cgraph_node failed
  | # 02:00:33 lto1: error: direct call to linux_libc_has_function/154258 in speculative call sequence has speculative_id 256 out of range
  | # 02:00:33 lto1: error: direct call to linux_libc_has_function/154258 in speculative call sequence has speculative_id 257 out of range
  | # 02:00:33 lto1: error: direct call to linux_libc_has_function/154258 in speculative call sequence has speculative_id 258 out of range
  | # 02:00:33 lto1: error: direct call to linux_libc_has_function/154258 in speculative call sequence has speculative_id 259 out of range
  | # 02:00:33 lto1: error: direct call to linux_libc_has_function/154258 in speculative call sequence has speculative_id 260 out of range
  | # 02:00:33 lto1: error: direct call to default_floatn_builtin_p/72810 in speculative call sequence has speculative_id 261 out of range
  | # 02:00:33 lto1: error: direct call to default_floatn_builtin_p/72810 in speculative call sequence has speculative_id 262 out of range
  | # 02:00:33 lto1: error: direct call to default_floatn_builtin_p/72810 in speculative call sequence has speculative_id 263 out of range
  | # 02:00:33 lto1: error: direct call to default_floatn_builtin_p/72810 in speculative call sequence has speculative_id 264 out of range
  | 
  | From
  | # reset_artifacts:
  | -10
  | # true:
  | 0
  | # build_abe bootstrap_profiled_lto:
  | 1

Used configuration :
 *CI config* tcwg_bootstrap_build master-aarch64-bootstrap_profiled_lto
 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu

We track this bug report under https://linaro.atlassian.net/browse/GNU-1801. 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
 * https://ci.linaro.org/job/tcwg_bootstrap_build--master-aarch64-bootstrap_profiled_lto-build/1015/artifact/artifacts/
The full lists of regressions and improvements as well as configure and make commands are in
 * https://ci.linaro.org/job/tcwg_bootstrap_build--master-aarch64-bootstrap_profiled_lto-build/1015/artifact/artifacts/notify/

Current build   : https://ci.linaro.org/job/tcwg_bootstrap_build--master-aarch64-bootstrap_profiled_lto-build/1015/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-aarch64-bootstrap_profiled_lto-build/1014/artifact/artifacts

Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1/1e314be3ccc50dc7dcf0ad6c3aebe63cf025f4bf/tcwg_bootstrap_build/master-aarch64-bootstrap_profiled_lto/reproduction_instructions.txt

Full commit : See in git+ssh://[email protected]/git/gcc.git
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.