Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_ubsan updated (44d1137d66 -> 5cfab6befa)

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_ubsan in repository toolchain/ci/base-artifacts. from 44d1137d66 60: onsuccess: #470: 2: Success after binutils/gcc: 25 commits new 5cfab6befa 61: onsuccess: #471: 2: Success after binutils/gcc: 16 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 1672 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50308 -> 51324 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 530508 -> 533496 bytes 06-check_regression/console.log.xz | Bin 2868 -> 3084 bytes 07-update_baseline/console.log | 2 +- 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 | 18 +++++++++--------- 13 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[linux] branch master updated (b357fd1c2afc -> a962b54e162c)

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 linux. from b357fd1c2afc Merge tag 'usb-6.0-final' of git://git.kernel.org/pub/scm/ [...] new efd608fa7403 x86/alternative: Fix race in try_get_desc() new df5b035b5683 x86/cacheinfo: Add a cpu_llc_shared_mask() UP variant new 534b0abc627a Merge tag 'x86_urgent_for_v6.0' of git://git.kernel.org/pu [...] new 24919fdea6f8 perf/x86/intel: Fix unchecked MSR access error for Alder Lake N new f2aeea57504c perf/x86/core: Completely disable guest PEBS via guest's g [...] new 6b959ba22d34 perf/core: Fix reentry problem in perf_output_read_group() new febae48afe60 Merge tag 'perf-urgent-2022-10-02' of git://git.kernel.org [...] new f938a5295ced dt-bindings: i2c: st,stm32-i2c: Document interrupt-names property new 367d4c887acd dt-bindings: i2c: st,stm32-i2c: Document wakeup-source property new e2062df704de i2c: davinci: fix PM disable depth imbalance in davinci_i2c_probe new a962b54e162c Merge tag 'i2c-for-6.0-rc8' of git://git.kernel.org/pub/sc [...] The 11 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: .../devicetree/bindings/i2c/st,stm32-i2c.yaml | 7 ++++ arch/x86/events/intel/core.c | 40 ++++++++++++++++++- arch/x86/events/intel/ds.c | 9 ++++- arch/x86/events/perf_event.h | 2 + arch/x86/include/asm/smp.h | 25 +++++++----- arch/x86/kernel/alternative.c | 45 +++++++++++----------- drivers/i2c/busses/i2c-davinci.c | 3 +- kernel/events/core.c | 9 +++++ 8 files changed, 104 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (6deb7a8185b -> c3d64d467d4)

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 6deb7a8185b gdb/disasm: better intel flavour disassembly styling with Pygments new c3d64d467d4 gdb/testsuite: handle invalid .exp names passed in TESTS 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: gdb/testsuite/Makefile.in | 40 ++++++++++++++++++++++++++++++---------- 1 file changed, 30 insertions(+), 10 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/master-aarch64-check_bootstrap_lto updated (74f385d7d9 -> 9792be1b1d)

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_check_bootstrap/master-aarch64-check_bootstrap_lto in repository toolchain/ci/base-artifacts. from 74f385d7d9 51: onsuccess: #593: 1: Success after binutils/gcc: 27 commits new 9792be1b1d 52: onsuccess: #594: 1: Success after binutils/gcc: 15 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 1760 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 37724 -> 38404 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 273344 -> 276800 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3820 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2740 -> 2860 bytes 07-check_regression/console.log.xz | Bin 5876 -> 5200 bytes 07-check_regression/mail-body.txt | 27 - 07-check_regression/results.compare | 41 +- 07-check_regression/results.compare2 | 245 +- 08-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3610260 -> 3619788 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 3254836 -> 3241496 bytes sumfiles/gcc.sum | 4740 +++++++++++------------ sumfiles/gfortran.log.xz | Bin 1083120 -> 1078744 bytes sumfiles/gfortran.sum | 74 +- sumfiles/libatomic.log.xz | Bin 2356 -> 2352 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213976 -> 214188 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465552 -> 465536 bytes sumfiles/libstdc++.sum | 10 +- 32 files changed, 2571 insertions(+), 2792 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allnoconfig updated (3e46a85412 -> 805d3bca47)

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-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from 3e46a85412 12: onsuccess: #402: all: Success after binutils/llvm/linux/ [...] new 805d3bca47 13: onsuccess: #403: all: Success after binutils/llvm/linux/ [...] 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 1708 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 29804 -> 30784 bytes 04-build_kernel_llvm/console.log.xz | Bin 64464 -> 64860 bytes 05-build_abe-qemu/console.log.xz | Bin 31020 -> 31688 bytes 06-build_linux/console.log.xz | Bin 556136 -> 3168 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4480 -> 4456 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (637b2f86138 -> 6deb7a8185b)

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 637b2f86138 gdb: update now gdbarch_register_name doesn't return nullptr new 5b0e2b48edb gdb/testsuite: extend styling test for libopcodes styling new f22c50c22cb gdb: improve disassembler styling when Pygments raises an e [...] new 6deb7a8185b gdb/disasm: better intel flavour disassembly styling with Pygments The 3 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: gdb/disasm.c | 69 +++++++++++------ gdb/disasm.h | 21 +++++- gdb/python/lib/gdb/styling.py | 59 ++++++++++++++- gdb/testsuite/gdb.base/style.exp | 159 +++++++++++++++++++++++++++++++-------- 4 files changed, 250 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (08f406e9a1e -> 637b2f86138)

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 08f406e9a1e gdb/mi: new options for -data-disassemble command new e7b1ba07bc9 gdb/testsuite: rewrite capture_command_output proc new bd93abe8d55 gdb/riscv: fix failure in gdb.base/completion.exp new 89e601ac3a2 gdb/gdbarch: add a comment to gdbarch_register_name new 9a972b54040 gdb: add a gdbarch_register_name self test, and fix some ar [...] new 9a103324fee gdb: check for duplicate register names in selftest new 7df42400402 gdb: add asserts to gdbarch_register_name new 7ac20d65a8d gdb/csky: remove nullptr return from csky_pseudo_register_name new 9b9e61c7cf4 gdb: final cleanup of various gdbarch_register_name methods new 637b2f86138 gdb: update now gdbarch_register_name doesn't return nullptr The 9 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: gdb/alpha-tdep.c | 8 +-- gdb/arch-utils.c | 3 +- gdb/avr-tdep.c | 6 +-- gdb/bpf-tdep.c | 5 +- gdb/cris-tdep.c | 7 +-- gdb/csky-linux-tdep.c | 14 ++--- gdb/csky-tdep.c | 20 ++----- gdb/features/rs6000/powerpc-604.c | 13 +++-- gdb/features/rs6000/powerpc-604.xml | 1 - gdb/features/rs6000/powerpc-750.c | 1 - gdb/features/rs6000/powerpc-750.xml | 1 - gdb/frv-tdep.c | 6 --- gdb/ft32-tdep.c | 5 +- gdb/gdbarch-components.py | 23 ++++++++ gdb/gdbarch-gen.h | 6 +++ gdb/gdbarch-selftests.c | 46 ++++++++++++++++ gdb/gdbarch.c | 6 ++- gdb/gdbarch.py | 21 +++++++- gdb/h8300-tdep.c | 11 ++-- gdb/hppa-tdep.c | 12 ++--- gdb/infcmd.c | 3 +- gdb/iq2000-tdep.c | 3 +- gdb/lm32-tdep.c | 6 +-- gdb/m32c-tdep.c | 8 +-- gdb/m32r-tdep.c | 5 +- gdb/m68hc11-tdep.c | 9 ++-- gdb/m68k-tdep.c | 9 ++-- gdb/mep-tdep.c | 2 +- gdb/mi/mi-main.c | 20 +++---- gdb/microblaze-tdep.c | 6 +-- gdb/mips-tdep.c | 8 +-- gdb/mn10300-tdep.c | 14 +++-- gdb/moxie-tdep.c | 5 +- gdb/msp430-tdep.c | 2 + gdb/nds32-tdep.c | 10 ++-- gdb/nios2-tdep.c | 2 +- gdb/regcache.c | 5 +- gdb/reggroups.c | 3 +- gdb/riscv-tdep.c | 34 ++++++------ gdb/sh-tdep.c | 103 +++++++++++------------------------- gdb/sparc-tdep.c | 8 +-- gdb/sparc64-tdep.c | 8 +-- gdb/testsuite/lib/gdb.exp | 35 ++++++++++-- gdb/tic6x-tdep.c | 3 -- gdb/tilegx-tdep.c | 8 +-- gdb/tui/tui-regs.c | 4 +- gdb/user-regs.c | 10 ++-- gdb/v850-tdep.c | 14 +++-- gdb/valops.c | 2 +- gdb/vax-tdep.c | 6 +-- gdb/xstormy16-tdep.c | 9 +--- gdb/xtensa-tdep.c | 6 +-- gdb/z80-tdep.c | 4 +- 53 files changed, 282 insertions(+), 307 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-defconfig updated (785909cb89 -> e331473e6e)

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-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from 785909cb89 11: onsuccess: #485: boot: Success after binutils/gcc/linux/ [...] new e331473e6e 12: onsuccess: #486: boot: Success after binutils/gcc/linux/ [...] 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 1708 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30896 -> 30952 bytes 04-build_abe-stage1/console.log.xz | Bin 72928 -> 72772 bytes 05-build_abe-qemu/console.log.xz | Bin 31512 -> 32380 bytes 06-build_linux/console.log.xz | Bin 3748 -> 3752 bytes 07-boot_linux/console.log.xz | Bin 6040 -> 6048 bytes 08-check_regression/console.log.xz | Bin 4416 -> 4328 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_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 | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (5ae928d7e8 -> 341aee75dd)

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 in repository toolchain/ci/base-artifacts. discards 5ae928d7e8 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits discards c5125356ad 157: onsuccess: #1562: 2: Success after gcc: 2 commits discards d3eb00b99b 156: onsuccess: #1561: 2: Success after gcc: 2 commits discards 3d5cce0f83 155: onsuccess: #1560: 2: Success after gcc: 3 commits discards 23614f30d6 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits discards ced6b6d078 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards 001eef3a50 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards 28e61fecf9 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards 93c4cbf520 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards 6273915269 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards 14b5ce7c49 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards 3d75ae8346 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 5fcbe65dde 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards 61f4dc7a10 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 35176fdd78 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards 4a14ea0283 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards b732245f12 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards be9d5fc2db 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 688e7f4252 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards aa9e29205b 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 7350d2d852 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 6c5513dfd8 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards a9ea4635b3 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards 2bffb098ee 135: force: #1540: 2: Success after gcc: 23 commits discards df0c1eae86 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 86dc881186 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 1ad89ec8a7 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 2bba7f94d2 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 00b9af7f0d 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 1d55b707b4 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 93025be92c 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 1c3a91f8ed 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards bde9f77821 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards be1f63921b 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 5961cda855 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards a356baed0e 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards ad016f49a5 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 67eaf9ed94 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards ceed5cdfcf 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 4344c8b88e 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 03b3419170 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 92a9cea3f4 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards e3b8f558f6 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 74a22d4696 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 5e7d9578bc 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 554b5543ee 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 04aea6ea48 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards e43e0a8f29 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards c9657f5cf4 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards b9281207e7 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 01e95c9bd1 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards a85a68bda4 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards c996569db5 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards f67beaeb73 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards e19923d0a3 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 219da72dd9 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 1ac28dd3f7 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 3ddfbe0c18 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 6a5f189d0a 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 260d2405dd 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards f782bf07fe 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 703db77977 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards a8b6700cb0 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards ba72be9a20 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 46f14d0e26 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 970f0a6959 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 619bcdf09e 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 434348c56f 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 440630ba00 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 39eb991de3 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 5947af51af 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards f6a951ea2d 87: onsuccess: 2: Success after gcc: 4 commits discards 89c5b807d5 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards e319e871c7 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 02d96cf8fa 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 6a60f85a66 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 3bc3cc9d92 82: onsuccess: 1: Successful build after gcc: 3 commits discards ca80738103 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 77948c77d0 80: force: 2: Successful build after gcc: 14 commits discards a30d1e5290 79: onsuccess: 2: Successful build after binutils: 5 commits discards f1a10f8fc4 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards b561ec64d2 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 27b86d3c11 76: onsuccess: 2: Successful build after gcc: 12 commits discards 38009496c0 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 6c9c291e56 74: onsuccess: 2: Successful build after baseline build: no [...] discards 50d5b546b9 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards c400a96cdb 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ce35d37fca 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards fe9384d82b 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6ffb176786 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5e34f3644b 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards d6a3e0310f 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e2a6962afb 66: onsuccess: 2: Successful build after gcc: 9 commits discards a1a58657a0 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 2f2b6153f1 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 084e7a55d7 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9a21e676f4 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 88df68db70 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 55edbf950b 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 8b083989f3 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards ed03baa057 58: force: 2: Successful build after gcc: 6 commits new 9d568750fa 58: force: 2: Successful build after gcc: 6 commits new d61bd4220f 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new c95b280acf 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new b8a9ed3c1b 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new e0ff3813aa 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 7a3aa34c5c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new eca03b4b20 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 90cf1c0251 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ad5c84a0cb 66: onsuccess: 2: Successful build after gcc: 9 commits new 250b4007e7 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1f0a806bd3 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 57ef459b3e 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c70c9d8faf 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 6268f9d9aa 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 014c2de609 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c64f3bf4fd 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 8fc6353754 74: onsuccess: 2: Successful build after baseline build: no [...] new 4fce825e98 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 07dc3dfdc6 76: onsuccess: 2: Successful build after gcc: 12 commits new db434aedc8 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 56ef02956d 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new a770eb4320 79: onsuccess: 2: Successful build after binutils: 5 commits new e4484f7af0 80: force: 2: Successful build after gcc: 14 commits new fabd283813 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 85cd99697e 82: onsuccess: 1: Successful build after gcc: 3 commits new 7f56265841 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new ce6719b230 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 4359658086 85: onsuccess: 2: Success after binutils/gcc: 25 commits new d64dc01248 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 34c30da9a6 87: onsuccess: 2: Success after gcc: 4 commits new affb04e5be 88: onsuccess: 2: Success after binutils/gcc: 25 commits new e0b26fae6f 89: onsuccess: 2: Success after binutils/gcc: 4 commits new ac926b1523 90: onsuccess: 2: Success after binutils/gcc: 16 commits new e7812a3b1d 91: onsuccess: 2: Success after binutils/gcc: 7 commits new a3ee6e9c31 92: onsuccess: 2: Success after binutils/gcc: 9 commits new f52b1f289a 93: onsuccess: 2: Success after binutils/gcc: 3 commits new b8fa6b2db3 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 84d7d39ca1 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 5c313dd43e 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 241071d2ad 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 4a79a502fe 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 95a18b5a38 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 28b3a16048 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 4658ca736b 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 86a54b9721 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new ef3c00bc37 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 38d9226b13 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 533a0f2a8e 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 24f73ca604 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 38dc8900aa 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 1c4cdf24c4 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 5baed27ed0 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new b0835f4f33 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 6970f1af20 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 431f70fb9e 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new dab034465a 113: onsuccess: #1514: 2: Success after gcc: 5 commits new ff4e51e482 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 1b59aa5868 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 73b00ca18f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 83283c4a56 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 8f0de45a96 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 393c3a5684 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 5115e264ad 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new aaddc43704 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 3e3f6cad23 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new abf5393a55 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 8b0a34e649 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new ba22158b3f 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new af5d184481 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 821530f6b4 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 8263fa2229 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 8c3234a815 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 3874e62338 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new ac1524020a 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 0e5ea3caa9 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 7aa2387fe6 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new c5de971989 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 8d4ffbb79f 135: force: #1540: 2: Success after gcc: 23 commits new c490ac0034 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 20b4ba9386 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 59ddeab559 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 097ce66972 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 5015dc1536 140: onsuccess: #1545: 1: Success after gcc: 7 commits new e7f6120ada 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 5e2c689a1a 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 37bd41a22c 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new aecc1ecb77 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 148c090f65 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new cd8699f0ce 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new 73459c7691 147: onsuccess: #1552: 1: Success after gcc: 2 commits new 5fbb797adc 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new e31b85fd0a 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new 8388951d85 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 4ea5471864 151: onsuccess: #1556: 2: Success after binutils: 12 commits new c8a1dcc399 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new acb4df430f 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new 0339688032 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits new 4c5c522c09 155: onsuccess: #1560: 2: Success after gcc: 3 commits new f603304fd6 156: onsuccess: #1561: 2: Success after gcc: 2 commits new 83948e1737 157: onsuccess: #1562: 2: Success after gcc: 2 commits new 60294a6683 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits new 341aee75dd 159: onsuccess: #1564: 2: Success after binutils/gcc: 11 commits 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 (5ae928d7e8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1672 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 51324 -> 51524 bytes 05-build_abe-bootstrap/console.log.xz | Bin 465744 -> 464884 bytes 06-check_regression/console.log.xz | Bin 2540 -> 3052 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- 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 | 18 +++++----- 13 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (782c15e279 -> ebccba794d)

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-arm in repository toolchain/ci/base-artifacts. discards 782c15e279 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards fc4734cff9 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 439bf6db34 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards b8e71afc96 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 835809e8e2 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards b25bc19c66 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards d9ce77a6e4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards a83196d85b 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards a58df84cdb 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 5df45acfa4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 0ab8704a96 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 277c2578d2 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 7b59f5e7a2 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 9b0c62a331 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 459268cc21 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 4145032150 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 1539a087b8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 927ec93fa3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 4034d8c2b8 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e6c48e643c 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards cc52c1ea0a 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards d4fa75bfde 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 61d96312cc 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 788b158f1d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards b37149d27c 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards a7fb194afd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 7018865cf1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 2678572c4e 128: onsuccess: #1723: 1: Success after linux: 12 commits discards b8633c3f9c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4714590f5f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 347215527d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 6d5b202f22 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 02b0833778 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards d407d27e55 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 7fc8b849c7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards ffe21f6a10 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 13c677f027 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards d16de88b59 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 87af198a63 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 7d86e378b8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards f798298e80 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 6d3e12e92a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 197421cef5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards a01c16fa57 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards f65076c256 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards dfbc9deb0c 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 194297f8f1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 7bafa89633 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 21451aa70a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 8c443b42c5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 8179d129b5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 8f83c67218 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 14eb40d58d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 0cd5cf68c6 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 81c8d77316 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 0eb707729d 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards a8b01858c0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 95cb27af6f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 71f73b2969 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 16cceaa7df 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards bb560e45ee 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 8345610ea1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 21573f47ed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b92e83bec0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 947a4bac27 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 8b88393473 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ee46a68547 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c3a3910b30 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards a38245a177 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 23eb873116 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 64a1de7507 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 3f47e8f14f 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 10e1a05c19 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards bb05826da9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards cbadbad84c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards e6eb2bad3f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 7602705a5f 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 54a8a93d22 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 65103ae17b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6cabba42c2 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards bb4fa8c424 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 28d897959c 74: onsuccess: 1: Successful build after linux: 44 commits discards 838f3dd98c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6cd38c226a 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8b7ec4ded4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 0ac8b36af8 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 4228b0f2ad 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 6c60ef15f4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 97ed350313 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8130da6213 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a6f24dc039 65: onsuccess: 1: Successful build after gcc: 4 commits discards 012eba71a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6831f0f2f5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b1d8f12ace 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 74d589a6bd 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards dca794fe44 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b2df515570 59: onsuccess: 1: Successful build after glibc: 2 commits discards 1414b5a3c0 58: onsuccess: 1: Successful build after binutils: 2 commits discards bff3df3c20 57: onsuccess: 1: Successful build after gcc: 7 commits discards 0d704ec40b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9ad8167a90 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new be34df0668 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 84c6ccb287 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 56daf03552 57: onsuccess: 1: Successful build after gcc: 7 commits new 08086c420d 58: onsuccess: 1: Successful build after binutils: 2 commits new b2e49a621c 59: onsuccess: 1: Successful build after glibc: 2 commits new 3b05677f0f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 874dfe7435 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 268335eaf3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new fa861a46ed 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new baa3f1cf7e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0249e4d029 65: onsuccess: 1: Successful build after gcc: 4 commits new f907217910 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ca05f5fd8f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ee8eb078e6 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b1205e8f33 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 37947d456b 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 1ff93305a6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 9572351a85 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ebfa0dd5df 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new da50b2ab01 74: onsuccess: 1: Successful build after linux: 44 commits new e4622fe5a2 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fafbe541dd 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 12effb090d 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 54bbdd9ed9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4a97824bd5 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 29de8d109c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new baf77675ba 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 96f0f69f72 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 7008d1464e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new e1324f9c99 84: onsuccess: 1: Success after gcc/glibc: 9 commits new f8c5b3f397 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new c9c5729a86 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new eed676315e 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3be5d40b63 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 2762a9c258 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6799706386 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6e48fe47cc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 9b06b11a67 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 78367c3d1d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new dc8197d646 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 7e7dfb3787 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b79f965a52 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new e1579594d5 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new a65b879e18 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 079e9018b8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new aeb5bfb8f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new b28e5da168 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b20af5dd17 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new f136f97440 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 4e323516b4 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 379d2fc911 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 7cac034bd5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 52af317d70 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new f1d8afdf6c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 5301abe0b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3f30ad3e83 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 7135137f33 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 5e440d9da4 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 26df55c527 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new a33ce18f1f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new a20147f819 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new bc99b41690 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new ed681e6fbd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 06c6b51e1c 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 185600ea17 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 6de7ad4fc2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new a3e97142c5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 3c0032822e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 9b6387d3ca 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new ca36de303c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 809b2f0401 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a6b05eee0b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 85f401c44a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 2d9ff1f765 128: onsuccess: #1723: 1: Success after linux: 12 commits new 7bcad40a59 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 9cae6bef7d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 65929ff61f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new da93af8e04 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 49652ca0f5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new a2f8477937 134: onsuccess: #1730: 1: Success after binutils: 2 commits new d06f5f0aba 135: onsuccess: #1733: 1: Success after binutils: 5 commits new e41b02d3ad 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 553467d5c5 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a1088150c6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 3beebe4241 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new fa09e80cb4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 0c777cc9cb 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new e882f855b6 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 1b777fe23b 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new e337db5fce 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 9f57a6cd68 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 2b2c3b52d1 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new afaabcc932 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 6348b003eb 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new dd8390e727 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new dcfcbb4533 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 3a84a02c5b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new fabfa1ac5e 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 1cd151a29d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 62d59b4e77 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 9af2fa35c8 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new ebccba794d 156: onsuccess: #1757: 1: Success after gcc: 4 commits 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 (782c15e279) \ 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 1668 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30112 -> 30076 bytes 04-build_abe-stage1/console.log.xz | Bin 90876 -> 90648 bytes 06-build_abe-linux/console.log.xz | Bin 8928 -> 8956 bytes 07-build_abe-glibc/console.log.xz | Bin 234276 -> 233936 bytes 08-build_abe-stage2/console.log.xz | Bin 223936 -> 223468 bytes 09-build_abe-gdb/console.log.xz | Bin 37120 -> 37192 bytes 10-build_abe-qemu/console.log.xz | Bin 31540 -> 32072 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2872 bytes 13-check_regression/console.log.xz | Bin 5700 -> 5688 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 44 +- 13-check_regression/results.compare | 18 +- 13-check_regression/results.compare2 | 19 +- 13-check_regression/results.regressions | 18 +- 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 18 +- sumfiles/g++.log.xz | Bin 2664664 -> 2696696 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2232560 -> 2205840 bytes sumfiles/gcc.sum | 2602 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 886828 -> 887700 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201752 -> 201532 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423444 -> 432028 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 1476 insertions(+), 1423 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022