Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_fx/gnu-master-aarch64-cpu2017rate-O3_SVE updated (2f32d06e3b -> 7a4e5d5ad2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_fx/gnu-master-aarch64-cpu2017rate-O3_SVE in repository toolchain/ci/base-artifacts. from 2f32d06e3b 4: onsuccess: #8: 1: [TCWG CI] No change after binutils/gcc/ [...] new 7a4e5d5ad2 5: onsuccess: #9: 1: [TCWG CI] No change after binutils/gcc/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30472 -> 30416 bytes 04-build_abe-stage1/console.log.xz | Bin 72700 -> 71268 bytes 06-build_abe-linux/console.log.xz | Bin 8680 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 242932 -> 243276 bytes 08-build_abe-stage2/console.log.xz | Bin 177180 -> 176212 bytes 09-benchmark/benchmark-build.log | 88 +- 09-benchmark/benchmark.log | 86 +- 09-benchmark/console.log.xz | Bin 3724 -> 3708 bytes 10-check_regression/console.log.xz | Bin 11516 -> 11356 bytes .../csv-results-vs-first-1/md5sum.csv | 1724 +- .../csv-results-vs-first-1/perf.csv | 2347 +- .../csv-results-vs-first-1/results.csv | 19489 ++++------- .../csv-results-vs-first-1/size.csv | 16780 ++++------ .../csv-results-vs-first-1/vect.csv | 278 +- .../csv-results-vs-prev-0/md5sum.csv | 1884 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2448 +- .../csv-results-vs-prev-0/results.csv | 32384 ++++++------------- 10-check_regression/csv-results-vs-prev-0/size.csv | 29749 +++++------------ 10-check_regression/csv-results-vs-prev-0/vect.csv | 1385 +- .../csv-results-vs-prev-1/md5sum.csv | 1724 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2347 +- .../csv-results-vs-prev-1/results.csv | 19489 ++++------- 10-check_regression/csv-results-vs-prev-1/size.csv | 16780 ++++------ 10-check_regression/csv-results-vs-prev-1/vect.csv | 278 +- 10-check_regression/results-vs-first-brief.csv | 42 +- 10-check_regression/results-vs-first-full.csv | 2433 +- 10-check_regression/results-vs-first-internal.csv | 174 +- 10-check_regression/results-vs-first.csv | 174 +- 10-check_regression/results-vs-first.log | 610 +- 10-check_regression/results-vs-prev-brief.csv | 48 +- 10-check_regression/results-vs-prev-full.csv | 2527 +- 10-check_regression/results-vs-prev-internal.csv | 182 +- 10-check_regression/results-vs-prev.csv | 182 +- 10-check_regression/results-vs-prev.log | 665 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 14 +- .../500.perlbench_r/results-metrics.json | 4 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 14 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../503.bwaves_r/results-metadata.json | 14 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 14 +- .../507.cactuBSSN_r/results-metadata.json | 14 +- .../508.namd_r/results-metadata.json | 14 +- .../510.parest_r/results-metadata.json | 14 +- .../510.parest_r/results-metrics.json | 6 +- .../511.povray_r/results-metadata.json | 14 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 14 +- .../520.omnetpp_r/results-metadata.json | 14 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 14 +- .../523.xalancbmk_r/results-metadata.json | 14 +- .../525.x264_r/results-metadata.json | 14 +- .../526.blender_r/results-metadata.json | 14 +- .../526.blender_r/results-metrics.json | 2 +- .../527.cam4_r/results-metadata.json | 14 +- .../531.deepsjeng_r/results-metadata.json | 14 +- .../531.deepsjeng_r/results-metrics.json | 4 +- .../538.imagick_r/results-metadata.json | 14 +- .../541.leela_r/results-metadata.json | 14 +- .../squad-vs-first/544.nab_r/results-metadata.json | 14 +- .../squad-vs-first/544.nab_r/results-metrics.json | 2 +- .../548.exchange2_r/results-metadata.json | 14 +- .../549.fotonik3d_r/results-metadata.json | 14 +- .../554.roms_r/results-metadata.json | 14 +- .../squad-vs-first/554.roms_r/results-metrics.json | 2 +- .../squad-vs-first/557.xz_r/results-metadata.json | 14 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 33 +- mail/mail-body.txt | 33 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 78 files changed, 53972 insertions(+), 102893 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[gcc] branch master updated (bd044dae51c -> 203b127fccc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from bd044dae51c sphinx: add missing newline for conf.py files. new 203b127fccc Restore CCP copy propagation The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.dg/tree-ssa/ssa-ccp-42.c | 26 ++++++++++++++++++++++++++ gcc/tree-ssa-ccp.cc | 7 ++++++- 2 files changed, 32 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gcc.dg/tree-ssa/ssa-ccp-42.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allyesconfig updated (60bbf9f680 -> b93a12d969)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 60bbf9f680 25: onsuccess: #484: 33: Success after binutils/gcc/qemu: 19 [...] new b93a12d969 26: onsuccess: #485: 33: Success after binutils/gcc/qemu: 38 [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1876 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30172 -> 30192 bytes 04-build_abe-stage1/console.log.xz | Bin 91004 -> 90500 bytes 05-build_abe-qemu/console.log.xz | Bin 31560 -> 31500 bytes 06-build_linux/console.log.xz | Bin 5100 -> 5052 bytes 08-check_regression/console.log.xz | Bin 3988 -> 3916 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 updated (f8a93750c7 -> ef705e5317)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards f8a93750c7 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 3fb9955778 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] discards bd6ec85868 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] discards 9fc36e51bc 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] discards f2516f83b9 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] discards ebc6600065 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] discards 613ab3a20f 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] discards 129641df39 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] discards da34cdf336 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] discards b6014ca5be 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] discards 61842e7e7c 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] discards 70d26dfabb 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] discards dc0b3a1333 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] discards 66331b8579 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] discards 2dee32549e 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] discards c96c53f1dd 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] discards 13043eccb6 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] discards c5273c4055 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] discards 9c7d35e3b2 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] discards aead210dd1 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] discards 71b55fabed 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] discards d5ad57febb 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards dfbac7449e 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] discards 5c9f3f0f75 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] discards 736bbfad6a 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] discards d3c2af1d74 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 05ffdefafb 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] discards e63f99d269 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] discards bb8a41addf 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] discards 14fb7d4bea 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] discards dc845baf9b 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 2eb24bb7fd 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-gb [...] discards ea722b05e6 68: force: #484: 6: Success after gdb: 6 commits discards 0044bf3778 67: onsuccess: #483: 6: Success after linux: 384 commits discards cbf4469fa2 66: onsuccess: #482: 6: Success after glibc: 2 commits discards 1297eba50e 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 27684eefa8 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 94a46d16ce 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 60509face1 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 1cfb879c4b 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards 3874620c2f 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gli [...] discards 79be1f9b60 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards e274bcf1db 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 0e5297e3c0 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gdb [...] discards a1b127937e 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards 0e1991b6ec 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 64bd0df6de 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards 826d1bda50 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards 24ffed7146 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards 78533e8c2e 51: onsuccess: #465: 1: Success after gcc: 10 commits discards 6eeefcfd88 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb0 [...] discards 056244799a 49: force: #463: 6: Success after gcc: 18 commits discards c059a2e533 48: onsuccess: #461: 6: Success after binutils: 10 commits discards 1e4e2ae668 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gdb [...] discards a5f78b4ed2 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gdb [...] discards 6f5c73fc0e 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gli [...] discards 96c8dbcdd5 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gli [...] discards 95408ddf2b 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards ade0e645c2 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gli [...] discards 09f3aad169 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gdb [...] discards d3f7f980ab 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gli [...] discards 168164a0a0 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gdb [...] discards 5d83f6802c 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards 457f25096d 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gdb [...] discards 27102a06df 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gdb [...] discards 4b3d0d4348 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gli [...] discards 78e4e40428 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gli [...] discards 6640e4ea08 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gdb [...] discards 37111d7994 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gli [...] discards c082944ec2 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gli [...] discards 2e6adc3a77 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gli [...] discards 42074e5df1 29: onsuccess: #441: 6: Success after binutils/gcc/glibc/gdb [...] discards c14d776000 28: onsuccess: #440: 6: Success after binutils/gcc/linux/gli [...] discards 1a5d6a01e6 27: onsuccess: #439: 6: Success after binutils/gcc/linux/gli [...] discards 0d4cc9ec84 26: onsuccess: #438: 6: Success after binutils/gcc/linux/gdb [...] discards 944f3bf794 25: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards bf33734816 24: onsuccess: #436: 6: Success after binutils/gcc/linux/gdb [...] discards 803e65e561 23: onsuccess: 6: Success after binutils/gcc/linux/gdb: 125 commits discards a20929c55d 22: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards eae6807966 21: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards 39531deb23 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 3d9564b6b1 19: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards e58195aeb1 18: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 181f4a0f2f 17: onsuccess: 6: Successful build after binutils/gcc/glibc/ [...] discards 277ee2fcd2 16: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 8cd7c1137e 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 94f9e8432f 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 32de025f2c 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards ccb35f2019 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards d91bbe0af2 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 0fb8add3c2 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards c64011b262 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] discards 14d504e2e0 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] discards 135d3ce0af 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 94da8bd84b 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 7b3869af5f 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards c51412acf9 4: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 6d2c3088b7 3: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards d91d92114d 2: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 621b3e8e82 1: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 054cbea994 0: update: binutils-gcc-linux-glibc-gdb: 6 new 121ec773a4 0: update: binutils-gcc-linux-glibc-gdb: 6 new d2c3e27f4e 1: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 4e1a85aa50 2: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 85d8aaa91d 3: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 1ba502b156 4: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new f6706d7480 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new c0671ff91e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new cabbae21c1 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new e9ddabe952 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] new bd97c44a64 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] new 2a4cba350b 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 3d0c9395ac 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 78e5425585 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 8a4b264078 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 4c71902533 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 759f39cf1f 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 7fac6cb3f2 16: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 924cad1d4b 17: onsuccess: 6: Successful build after binutils/gcc/glibc/ [...] new df209380d4 18: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new d3d21472f8 19: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 5fa6f78893 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new d42fdcbd1a 21: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new 5106b32947 22: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new 81a30af263 23: onsuccess: 6: Success after binutils/gcc/linux/gdb: 125 commits new 2570f5cda6 24: onsuccess: #436: 6: Success after binutils/gcc/linux/gdb [...] new 0b272f4ce3 25: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new 35a4eac606 26: onsuccess: #438: 6: Success after binutils/gcc/linux/gdb [...] new c108003b63 27: onsuccess: #439: 6: Success after binutils/gcc/linux/gli [...] new b07e5401dd 28: onsuccess: #440: 6: Success after binutils/gcc/linux/gli [...] new be5af59b18 29: onsuccess: #441: 6: Success after binutils/gcc/glibc/gdb [...] new 1c14744701 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gli [...] new 78e771724a 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gli [...] new 99650ee5f0 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gli [...] new 10e403b866 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gdb [...] new 5b4dcc03de 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gli [...] new 472c010606 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gli [...] new 50bc013083 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gdb [...] new 0aa2b6bdb8 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gdb [...] new f3489612b4 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new 8512f0d481 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gdb [...] new b521db45d9 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gli [...] new 23a3cdb905 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gdb [...] new 029b5196d0 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gli [...] new 3651aaef87 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new 79f048bb16 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gli [...] new 3ec130781e 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gli [...] new b44ce7d96d 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gdb [...] new e492f775db 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gdb [...] new f83c0cec2f 48: onsuccess: #461: 6: Success after binutils: 10 commits new 0d8536b99f 49: force: #463: 6: Success after gcc: 18 commits new d2a03820c0 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new 979ab2a453 51: onsuccess: #465: 1: Success after gcc: 10 commits new 2dfd7c2644 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new 2a1a0aee8e 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 579a3ef8fc 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new 6be4f3eb06 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new 6659067f4d 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 2c7a6b3252 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gdb [...] new fe25a816d4 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 7ae276fd91 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 0d1f67052a 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gli [...] new e10623a139 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new e2a1da4c1f 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new c541620674 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 5923b0b844 64: onsuccess: #479: 6: Success after binutils: 14 commits new 81de07f67f 65: onsuccess: #480: 6: Success after gcc: 12 commits new 7c1298045b 66: onsuccess: #482: 6: Success after glibc: 2 commits new ec3a0bbf97 67: onsuccess: #483: 6: Success after linux: 384 commits new 7a26dea33d 68: force: #484: 6: Success after gdb: 6 commits new f50558235a 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-gb [...] new f71d4702d6 70: onsuccess: #486: 5: Success after gdb: 7 commits new 60632eb404 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] new 8bf2e36aca 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] new 3b91ed6e3e 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] new b9b102a6d7 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] new 7959bd1ade 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new ae5ab5ac89 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] new 3063116c7d 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] new 3d3032547b 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] new b57fe1020e 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 0dd9ad3588 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] new 6afb0057f5 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] new b2753f3d4c 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] new 664be5a88e 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] new 8e7c28b915 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] new 2569a0cd8f 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] new e060dbc557 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] new 60a55b36ab 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] new 2bcafeea4f 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] new 8625b4a595 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] new 6c1aaeb45e 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] new cf4c485d82 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] new 58bab5b4a0 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] new fbfd95cd55 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] new c3007bbc6d 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] new 0652f05b0c 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] new 97c6d7d426 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] new ebb30ca401 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] new 45f36b7768 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] new 2cd2ade2aa 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] new d6f6ad68ec 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new ef705e5317 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (f8a93750c7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1728 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 37796 -> 37948 bytes 05-build_abe-gcc/console.log.xz | Bin 213968 -> 213468 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8908 -> 8940 bytes 08-build_abe-glibc/console.log.xz | Bin 246540 -> 246352 bytes 09-build_abe-gdb/console.log.xz | Bin 38788 -> 38848 bytes 10-check_regression/console.log.xz | Bin 4420 -> 4496 bytes 11-update_baseline/console.log | 39 +++++++++++++++++++++++++++++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++----------------- 20 files changed, 63 insertions(+), 32 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[gcc] branch master updated (9e11ceef165 -> bd044dae51c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 9e11ceef165 unswitching of outer loops new bd044dae51c sphinx: add missing newline for conf.py files. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/d/doc/conf.py | 2 +- gcc/doc/cpp/conf.py | 2 +- gcc/doc/cppinternals/conf.py | 2 +- gcc/doc/gcc/conf.py | 2 +- gcc/doc/gccint/conf.py | 2 +- gcc/doc/install/conf.py | 2 +- gcc/fortran/doc/gfc-internals/conf.py | 2 +- gcc/fortran/doc/gfortran/conf.py | 2 +- gcc/go/doc/conf.py | 2 +- libgomp/doc/conf.py | 2 +- libiberty/doc/conf.py | 2 +- libitm/doc/conf.py | 2 +- libquadmath/doc/conf.py | 2 +- 13 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (15282c73f8 -> 83c61381e9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 15282c73f8 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards d1da3d645c 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 2f3e2f3c8b 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 22e9d92d07 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards be27418f3e 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 26836351f2 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 10b648f802 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 6051634bd3 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards ca5969c472 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards db82c7c135 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 38c9dff533 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 293fbf0548 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 3a4f506710 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 9f827d972e 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 41954d3218 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards ac5c25573d 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 3c5bb7bbac 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards b4b8ae957a 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 81a7fcd582 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards a1f58d72d3 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 48d902071b 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 0cf7534360 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 02dc87f898 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards e3c1759a25 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 43eb32e7bc 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 1eec233534 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards da8c4b55a7 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards b71d1b3ccc 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 1b6bf08fae 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards d1d8609c63 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards aee7cbc74b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 8d10f47458 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards e51fd21124 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 86e4b08187 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 42d89c351b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 4f2d9bdd52 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 08c1d1a06d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards e4a062c680 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards c3bf09d270 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 0b1355c0be 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 912a62e07c 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 4464bea963 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards b4220f67e6 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 595ff9c0c7 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 4d33c4551f 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 629a5e31fc 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 1678fe8fa7 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 28ece5952e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards f0db7935f9 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards b664e2c1e6 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 020b8f2732 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 5aba8c1b98 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 38f0315791 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards fc2443d5eb 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards e4715aa402 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 60e04f12b5 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards b57b6107f2 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 97d0b2980b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 9ceeaff8a4 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 0d9b3fa7bd 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 4df1f4eb21 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 86d5802577 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 17907aedda 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 2db86f0e30 128: onsuccess: #2163: 1: Success after linux: 23 commits discards e0009371f9 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards e9a3c8dfff 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards b3efce2103 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 7e1a79abf2 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 83aa077db4 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 7bac9bf0dd 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 4febb92915 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 15b78750c4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 3464b14b84 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 6a3d29ab75 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 23d83320df 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards cb0a20d2a3 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 5df6f1117e 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 00c9f3fe8a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 4842dbc890 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 366971d84b 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards fc266178d9 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 3a948331e4 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 265c28ad66 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 9e894fea44 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 175abcb58e 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 43d16239b5 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards dec126a493 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards d0c8cf682d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 4277e7b4e4 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 032eb55b56 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 8b5095ae3e 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 951c7c6b04 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 33f120c7c4 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 81e844e3b6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 8b9eec6b93 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 9b3cee64c6 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 9d5f425a4a 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 9a49b24413 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 757455da1d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 05155c4ce1 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 13d41246f0 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 91d573ed87 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new e477b4a07a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c907ea4ac6 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 330f9881cc 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 552a960c83 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 0c4e8980ad 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 2171b46134 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new c6466221b1 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 19c156dbd8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 849e26beea 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new a3699b693f 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 8e63b40a24 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new dccaafc252 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 7bf83fc2d5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e379519de7 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 8af20e2663 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 19cd14ac69 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new b4fa52722b 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 39ba68237b 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 2196dd20b3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new ca687d20cf 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 87e848d951 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4361d24e4d 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new aebfcfaeb8 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new f7ca19dd02 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 3917d89028 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new d1fd2725eb 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 392eb63913 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 056de0dce5 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1016096244 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new e94235ec61 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 4842c9c087 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 24384a7dae 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new cdcca29149 124: onsuccess: #2159: 1: Success after linux: 23 commits new 86397927e6 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new b3dace8624 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 1cadeab843 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 86b04f53da 128: onsuccess: #2163: 1: Success after linux: 23 commits new 36d6e8a119 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 1c1519dbb6 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 668951a4e5 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 028e137268 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new b65a49c79a 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 530bc5acd7 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 73cfc488f7 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 14f0fbc30d 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 0c9a09398d 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3c900a4cfb 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new cd54789c6c 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 7b0a82d9b2 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 5f7d6758d7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 193e462515 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 9c93acd1bb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 02441b93e0 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 01cf50172f 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new ff0907a7a0 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 4a2c1f04d7 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new abc518312e 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 1c4764458b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 7833052b1e 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 7a8ffdce5e 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 8ded6f2c52 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 3868dadd86 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 13527b774f 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 531a4874ac 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 520e1f5725 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 434e77d749 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new ef34624ead 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new dc9a574bae 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 7ae525730e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new e4783ce991 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new f0e7cf55d9 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 4b194d9c86 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new b121d0b845 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 02ff49c743 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 17b231b048 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 5356fe94ce 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 90d2825951 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new c4f7b8128a 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 4c7ccf2175 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 64a5a83120 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 950e78d22b 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 4ea123ab77 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 8f7bfe0542 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new b903f2c5f5 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 275a4bb3d6 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new f27f65e505 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 18f77e8e64 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 10e247bb3e 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 7304efb6c2 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new dd38200e5a 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new f7be9f316b 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new d2904e58cf 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new eb43d75450 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new bb06ee14a7 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new b187baf80a 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new e34af2ea60 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new dfa55e8a3d 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 65b5c74072 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 94e9c2f22a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 1b2eaeb7b6 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 83c61381e9 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (15282c73f8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30532 -> 30772 bytes 04-build_abe-stage1/console.log.xz | Bin 73488 -> 71964 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8868 bytes 07-build_abe-glibc/console.log.xz | Bin 244696 -> 244488 bytes 08-build_abe-stage2/console.log.xz | Bin 204024 -> 203060 bytes 09-build_abe-gdb/console.log.xz | Bin 37892 -> 38108 bytes 10-build_abe-qemu/console.log.xz | Bin 31932 -> 31808 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3496 -> 2664 bytes 13-check_regression/console.log.xz | Bin 20704 -> 21892 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 408 +- 13-check_regression/mail-body.txt | 218 +- 13-check_regression/results.compare | 528 ++- 13-check_regression/results.compare2 | 6352 +++++++++++-------------- 13-check_regression/results.regressions | 154 +- 14-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 220 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 154 +- sumfiles/g++.log.xz | Bin 3433420 -> 3430724 bytes sumfiles/g++.sum | 242 +- sumfiles/gcc.log.xz | Bin 3044708 -> 3022616 bytes sumfiles/gcc.sum | 7783 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1042444 -> 1032356 bytes sumfiles/gfortran.sum | 91 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213556 -> 213660 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 431656 -> 422840 bytes sumfiles/libstdc++.sum | 22 +- 46 files changed, 8113 insertions(+), 8197 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allmodconfig updated (2736d39507 -> 3d6a9e703e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 2736d39507 30: onsuccess: #410: 23165: Success after binutils/linux/qem [...] new 3d6a9e703e 31: onsuccess: #411: 23165: Success after binutils/linux/qem [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30564 -> 29920 bytes 04-build_kernel_llvm/console.log.xz | Bin 64228 -> 63636 bytes 05-build_abe-qemu/console.log.xz | Bin 31724 -> 31000 bytes 06-build_linux/console.log.xz | Bin 4772 -> 4788 bytes 08-check_regression/console.log.xz | Bin 3712 -> 3760 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 updated (7a7590b1f5 -> 66af51da36)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O3 in repository toolchain/ci/base-artifacts. from 7a7590b1f5 92: onsuccess: #514: 2: Success after binutils/gcc: 58 commits new 66af51da36 93: onsuccess: #515: 2: Success after binutils/gcc: 47 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1668 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 51036 -> 51792 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 461068 -> 461288 bytes 06-check_regression/console.log.xz | Bin 3076 -> 3044 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/release-arm updated (63391d4154 -> 967d7b0710)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/release-arm in repository toolchain/ci/base-artifacts. from 63391d4154 30: onsuccess: #194: 1: Success after binutils/gcc/gdb: 11 commits new 967d7b0710 31: onsuccess: #195: 1: Success after binutils/gcc/glibc/gdb [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52308 -> 52312 bytes 04-build_abe-gcc/console.log.xz | Bin 228184 -> 229568 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8720 bytes 07-build_abe-glibc/console.log.xz | Bin 232188 -> 232784 bytes 08-build_abe-gdb/console.log.xz | Bin 46332 -> 46192 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3824 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2516 -> 2412 bytes 11-check_regression/console.log.xz | Bin 5284 -> 6220 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 56 +- 11-check_regression/results.regressions | 27 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 + sumfiles/g++.log.xz | Bin 2847704 -> 2865916 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2468436 -> 2469376 bytes sumfiles/gcc.sum | 5016 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 933472 -> 935628 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 211516 -> 212532 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457124 -> 463692 bytes sumfiles/libstdc++.sum | 12 +- 41 files changed, 2822 insertions(+), 2656 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

[binutils-gdb] branch master updated (ac71c620fd8 -> 1b377e49604)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from ac71c620fd8 mach-o reloc size overflow new 1b377e49604 ld/testsuite: skip ld-size when -shared is not supported The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: ld/testsuite/ld-size/size.exp | 6 ++++++ 1 file changed, 6 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 6 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022