Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[gcc] branch devel/omp/gcc-12 updated (4c7ad2bebbc -> 8cf4c2316cb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/omp/gcc-12 in repository gcc. from 4c7ad2bebbc openmp: Fix ICE with taskgroup at -O0 -fexceptions [PR107001] new dc09f5738e6 nvptx: forward '-v' command-line option to assembler new 38a225f9d39 nvptx: Make default '-misa=sm_30' explicit new 74ddd1ec9d8 nvptx: Introduce dummy multilib option for default '-misa=sm_30' new 8cf4c2316cb nvptx: Allow '--with-arch' to override the default '-misa' The 4 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/ChangeLog.omp | 40 +++++++++++++++++++++ gcc/config.gcc | 22 ++++++++++++ gcc/config/nvptx/gen-multilib-matches.sh | 60 ++++++++++++++++++++++++++++++++ gcc/config/nvptx/nvptx.cc | 4 +++ gcc/config/nvptx/nvptx.h | 8 +++++ gcc/config/nvptx/nvptx.opt | 2 +- gcc/config/nvptx/t-nvptx | 31 ++++++++++++++++- gcc/doc/install.texi | 9 +++++ gcc/doc/invoke.texi | 4 ++- 9 files changed, 177 insertions(+), 3 deletions(-) create mode 100755 gcc/config/nvptx/gen-multilib-matches.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (1e7e197974 -> 7c831cfbc7)

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_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 1e7e197974 44: onsuccess: #421: 2: Success after binutils/gcc: 11 commits new 7c831cfbc7 45: onsuccess: #422: 2: Success after binutils/gcc: 12 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 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 50080 -> 50412 bytes .../console.log.xz | Bin 941532 -> 938956 bytes 06-check_regression/console.log.xz | Bin 3076 -> 2768 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (1b74b5cb4e9 -> e9019085e17)

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 1b74b5cb4e9 [RFA] Minor improvement to coremark, avoid unconditional ju [...] new 84072a2615e nvptx: forward '-v' command-line option to assembler new 108b99b6c45 nvptx: Make default '-misa=sm_30' explicit new 4d94582e0dc nvptx: Introduce dummy multilib option for default '-misa=sm_30' new e9019085e17 nvptx: Allow '--with-arch' to override the default '-misa' The 4 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/config.gcc | 22 ++++++++++++ gcc/config/nvptx/gen-multilib-matches.sh | 60 ++++++++++++++++++++++++++++++++ gcc/config/nvptx/nvptx.cc | 4 +++ gcc/config/nvptx/nvptx.h | 8 +++++ gcc/config/nvptx/nvptx.opt | 2 +- gcc/config/nvptx/t-nvptx | 31 ++++++++++++++++- gcc/doc/install.texi | 9 +++++ gcc/doc/invoke.texi | 4 ++- 8 files changed, 137 insertions(+), 3 deletions(-) create mode 100755 gcc/config/nvptx/gen-multilib-matches.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (e456937d39 -> 72d69e3d42)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards e456937d39 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 50b5ef4a2a 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 559c692307 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 8de8a62e23 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards e66f1ffc4c 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards f05ac82c77 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards e1dd44f6bc 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards fec91e4a5a 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards e95aac6d43 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 6b6701df0f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 38a5879f04 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 9603ddbfa5 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards ca8c95c39c 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards bc94242aca 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 58cb903b29 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards c4572d725d 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 330f438ab4 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 7681bf4a42 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards b68db92a52 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 4394cf0754 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards a1afc918c8 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 8b53190241 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 0d744f3900 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 1f7b0d7c80 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards d52e3bf1a3 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards fd13d0ae34 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 192511df8f 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 2ce87b78b5 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards e60ec62513 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 611548b110 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 7f8ed5a5cb 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards a1dc62a137 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards a296b172a4 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 0838fc2aad 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 8afcc8f69e 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 06a4f6b230 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 9e14295391 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards daf142c007 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 396661a1ed 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 1d2772863c 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 112dfed7e5 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards e03b42728d 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards f651f562bc 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards b64b836911 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 06ac229cae 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 010781fc84 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards e35343b200 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards e6a7968bbb 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards d30da3f607 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 5521b0383d 85: onsuccess: 7: Success after gcc: 9 commits discards 07d666a88d 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 5450aed0cc 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 0a0c715747 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 283887700e 81: onsuccess: 7: Successful build after gcc: 2 commits discards ecbe90efe8 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 3ff84bc743 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards cf370828d0 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b15abbbafd 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 67b0e57320 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e8ff9032d8 75: onsuccess: 7: Successful build after linux: 44 commits discards 62d7fc4594 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 4011a7d30e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0d7a1aa3fb 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 6c3fc760c8 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 83dd63def7 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 1e567b9634 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7b31780260 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 724a4d35d2 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ffd86b0b58 66: onsuccess: 7: Successful build after gcc: 3 commits discards 09d4250a89 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5de09f964f 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 668b68e1fa 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 31fd40c883 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards bdbac432b6 61: onsuccess: 4: Successful build after gcc: 15 commits discards d673b20f08 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 2256aea482 59: force: 7: Successful build after gcc: 2 commits discards f8efb67a34 58: onsuccess: 7: Successful build after glibc: 2 commits discards f34ce7b92b 57: onsuccess: 7: Successful build after gcc: 7 commits discards ce2eddf81d 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ae6072cae3 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 42a2d9ca0b 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 4b8265e671 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 171ddc617b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 0c07fff0b8 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 509258379a 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bf7cfba389 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 84633431ab 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 78444f7dfa 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6e90042f5d 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 449934fcba 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 858ac6c3f6 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards b0b032b143 43: onsuccess: 7: Successful build after gcc: 2 commits discards 9eb10ce8a7 42: onsuccess: 7: Successful build after baseline build: no [...] discards 55f5ac5bd9 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bdf80761d7 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 708d127707 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] discards e07a278ec5 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards 20903c1514 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 03d2020c85 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b26839837b 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6ec83f1533 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new fb23bbddd3 34: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a9f20d8215 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 0a323a1bc2 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 786cebf2a2 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 31a02c2bb6 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 664cf5e93c 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 51e093e5f3 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f56353f24f 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6a3974bfc3 42: onsuccess: 7: Successful build after baseline build: no [...] new 39a67d5b4d 43: onsuccess: 7: Successful build after gcc: 2 commits new 63950d1aca 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new fb66441ca4 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3d0706547a 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new f7efc4dfc9 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0c5a8dac00 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new fc96380062 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 940ef2a007 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 89103dedce 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2c7a5cf762 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 2899b72a35 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 7897422afa 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new b5a474fd76 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new eecf778b51 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d148915e6d 57: onsuccess: 7: Successful build after gcc: 7 commits new 1324d6b2c8 58: onsuccess: 7: Successful build after glibc: 2 commits new 1835ca1de2 59: force: 7: Successful build after gcc: 2 commits new 7f6d1877b0 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new a239022c9b 61: onsuccess: 4: Successful build after gcc: 15 commits new df5e0ff1e2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 397c720c75 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 288cda3a4d 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 21f8f4915f 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a00073a1ae 66: onsuccess: 7: Successful build after gcc: 3 commits new d816d0261f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new ee8ffd9075 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 549d1b424b 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d3ae221a19 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 2bae7d61ab 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new e4677e1cd5 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new e0eecd16d3 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2b0dc3ae27 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new f2860b9a18 75: onsuccess: 7: Successful build after linux: 44 commits new e66df9cf7c 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0a6bcbf561 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 4cba28ecfe 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2bbd71ad74 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new acad788026 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 7824e9de19 81: onsuccess: 7: Successful build after gcc: 2 commits new 8a24d8e057 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 79ab2c7dba 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new ee748064e2 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new e2db5059f4 85: onsuccess: 7: Success after gcc: 9 commits new 7b8a3909c7 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 605b1647d1 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 77478f9628 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new c9284b677f 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new aee7029ff2 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 2abf021857 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a5284ad9b8 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 9dfa3d0a81 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new f8c17f2675 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 94b8253683 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new ed17d7d4e3 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 0bb41a0ad8 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 33316f66d9 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new ae69ab16a2 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 9b8c0788e1 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new d70527d4b9 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 745efdb692 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 0106cba6b2 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 5af0ee65b0 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new f43b99dd50 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new ffa680895f 106: onsuccess: #1617: 7: Success after gcc: 2 commits new d3ccbd1d16 107: onsuccess: #1618: 7: Success after gcc: 2 commits new fa754349d0 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new d1a15413da 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 58489606e4 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 90e14c28f7 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new b851f270af 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new dd23297265 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 3cd5164a8c 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 355d698ca8 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 474c58bca7 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 82a57eb15a 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new eed4f7c587 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new c66a3970b9 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new c74ce4324b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new cfa100d6b8 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 05cfde791b 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new d73e7ea455 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 94023fef04 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 58a961280b 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 0d5375c676 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new cf74c1eb03 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 9e0f95c3d5 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 3d3fa9f46d 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 33e9639fb0 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 66afe8b495 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 133166005f 132: onsuccess: #1645: 7: Success after linux: 23 commits new 8c82bfbce4 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new ed42b047d0 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 72d69e3d42 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] 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 (e456937d39) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 30092 -> 30184 bytes 05-build_abe-stage1/console.log.xz | Bin 91600 -> 90496 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8504 -> 8284 bytes 08-build_abe-glibc/console.log.xz | Bin 235552 -> 233284 bytes 09-build_abe-stage2/console.log.xz | Bin 224224 -> 223480 bytes 10-build_abe-gdb/console.log.xz | Bin 37444 -> 37444 bytes 11-build_abe-qemu/console.log.xz | Bin 31224 -> 31004 bytes 12-check_regression/console.log.xz | Bin 3872 -> 3836 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++-------- 20 files changed, 55 insertions(+), 55 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (386ebf75f4c -> 1b74b5cb4e9)

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 386ebf75f4c fix assert in __deregister_frame_info_bases new 1b74b5cb4e9 [RFA] Minor improvement to coremark, avoid unconditional ju [...] 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/cfgcleanup.cc | 2 +- gcc/cfgcleanup.h | 1 + gcc/cfgrtl.cc | 29 +++++++++++++++++++++++- gcc/testsuite/gcc.target/riscv/ret-1.c | 41 ++++++++++++++++++++++++++++++++++ 4 files changed, 71 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gcc.target/riscv/ret-1.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (b7b7d4e4d8 -> 7dc5c0c615)

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards b7b7d4e4d8 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 2bf9fd2b54 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 1dd56fb6f0 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 82dd46a22a 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards baa905d44b 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 0de0f78679 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 5f3a725f69 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards e4d108969f 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards f8ae356a46 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards b30fc886a9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 7eac1f0d83 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 8d0d623516 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 445ed45e48 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 060880f9cd 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards a58f2c22f9 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards c6795a01f4 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 323e36c533 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 416fb31393 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards f8d299dd5c 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 65285df470 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 91cf8e76b6 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards d869912a92 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 8c327dc529 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 0b51a7f738 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 6d5b135763 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 4676e66240 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 0c70898156 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 0fa5c23551 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 150b7525f5 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards f0582f4cf6 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 0f3a3f4b23 102: force: #1551: 1: Failure after gcc: 306 commits discards 742719998f 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 68d24f4fcc 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 14ea5769fb 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards be22171ce9 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 69466ff3aa 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards f3bb36c2c8 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards da6800b3bb 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3d2c08ae16 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards fb90e3624f 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 32c602f7ad 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards b00ca0a649 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 5d2113e5a3 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 4cbc0ab9d8 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 3117ba0f83 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 67a67e8d42 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 57b7d35033 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards c1d77f2ff7 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 8977287ddd 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f65d20a7c1 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 76d69fc9a1 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 3457dc6df5 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b76cc656c1 80: onsuccess: 7: Successful build after linux: 44 commits discards 1245280959 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards ede11013a3 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 74de3d5aa3 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4d3de123fd 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards ce8314f5dd 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 7f278d231c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards d89c6a9d0e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2f458d1643 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 38e9213b68 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2e44ebeffb 70: onsuccess: 7: Successful build after gcc: 4 commits discards e6b2b17f38 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cb1ae073f8 68: onsuccess: 7: Successful build after linux: 6 commits discards ffa4e1b485 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 2e6f75fd11 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 5bb4b4bbd0 65: onsuccess: 7: Successful build after binutils: 3 commits discards 44cbce9557 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 6a62341e94 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 7877113782 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 75f755bf4f 61: onsuccess: 4: Successful build after gcc: 5 commits discards 4162f5244b 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards f2205b2a24 59: force: 7: Successful build after gcc: 3 commits discards 212b45c9bd 58: onsuccess: 7: Successful build after glibc: 2 commits discards 0e0315b139 57: onsuccess: 7: Successful build after gcc: 7 commits discards 04b746bd81 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ef1f5c8236 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ef0ffdec21 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 59f80da260 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 38a6d6401d 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 91a1b0035b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 55903407ba 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cc6f2b7075 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards b5db327705 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 9b6e9ece75 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 827f76e6f9 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 306e2db145 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d2ff227e34 44: onsuccess: 7: Successful build after linux: 34 commits discards 5f4df47d8c 43: onsuccess: 7: Successful build after gcc: 2 commits discards 8af6562ae3 42: onsuccess: 7: Successful build after baseline build: no [...] discards be0faa85a0 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 51f958fcad 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1069bbde5a 39: onsuccess: 7: Successful build after gcc: 2 commits discards 7b768d1562 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d4885dacdf 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 918fa01ca1 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 96b5c0ab23 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards aac8306ed5 34: onsuccess: 7: Successful build after gcc: 3 commits discards d220059e4e 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bc639b9a7b 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new e59a758298 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new f08ccb2765 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7606523d3e 34: onsuccess: 7: Successful build after gcc: 3 commits new 9751a41ba6 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 828d6625f3 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6644199c39 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new cfd00d1ea4 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 16bad12ac3 39: onsuccess: 7: Successful build after gcc: 2 commits new 1dc5778ca2 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 023e46a86d 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 96efd7b491 42: onsuccess: 7: Successful build after baseline build: no [...] new 418bb4ad06 43: onsuccess: 7: Successful build after gcc: 2 commits new 8908395a6d 44: onsuccess: 7: Successful build after linux: 34 commits new fb847d5256 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 506f4b616f 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 1293e49f2f 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5c7ea67f22 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new c89aa12408 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new f7a0e0fc21 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6cb5a9a61f 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 87edc5bea6 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 0848eefa66 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 940272cebf 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 95a0ba1890 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b4a4c29c7a 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0d3ab8709d 57: onsuccess: 7: Successful build after gcc: 7 commits new c631da908d 58: onsuccess: 7: Successful build after glibc: 2 commits new 5b5fb44615 59: force: 7: Successful build after gcc: 3 commits new 6f0c0cbadf 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 23b8703d23 61: onsuccess: 4: Successful build after gcc: 5 commits new b33dacda01 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 12b296fdae 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new acae4fae45 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 6001161cbd 65: onsuccess: 7: Successful build after binutils: 3 commits new 59df334cf6 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 4eb82262fc 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 7b35954d59 68: onsuccess: 7: Successful build after linux: 6 commits new 19e82aa535 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e5a95af276 70: onsuccess: 7: Successful build after gcc: 4 commits new 29dd30ddf2 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 375f90d66f 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f36ee5feb9 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4af139a705 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 2e7f13dbee 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 5ad5eeebd9 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new af6aefcb90 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c2fc500ac4 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 475e2a03fc 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 39129ec0a1 80: onsuccess: 7: Successful build after linux: 44 commits new 1b67ac5647 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 978ee9368d 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 6c07529f58 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1b6cb212b0 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b48cc88a42 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 6770f66ead 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 38156a6be9 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new b66b51e7d6 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 53f4fadf70 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 7463476b6a 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 422a2bb723 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 0eb10f87f7 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 61ee7aab1e 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 4145c416ea 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 72b104ab4a 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new ec4f4ebe93 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 637ba47edc 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 0394991332 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 88e4c15663 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 3f69e7c7ba 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 589e8eef7d 101: onsuccess: #1547: 7: Success after binutils: 82 commits new b534da35ac 102: force: #1551: 1: Failure after gcc: 306 commits new 961a5fdfc5 103: onsuccess: #1552: 1: Success after gcc: 5 commits new e4325dce14 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new d92106cf32 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new ca3b5f6798 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new f1fb9f52bf 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new af4eff3f54 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 43603e7551 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 71bf7e6dcd 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 211c0a22b8 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 90975b3728 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 61d9d255c6 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 682482bb00 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 758b44861b 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 15efba37a7 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 8da4dcd5e2 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 20fdee6abe 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new f5190c0dae 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new df0305c0a4 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 842c1211d7 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new dba15214ba 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 47de8f02fe 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 5a02894b61 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new c3ae4e53a5 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 4a672e0a45 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new fffa4e3707 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 435882c940 128: onsuccess: #1579: 7: Success after linux: 12 commits new 52c2b7f39a 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new b7462d181c 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 7ef7b6489f 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 30ec593cf5 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 7dc5c0c615 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] 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 (b7b7d4e4d8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1716 -> 1636 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30228 -> 30420 bytes 05-build_abe-stage1/console.log.xz | Bin 72468 -> 72792 bytes 07-build_abe-linux/console.log.xz | Bin 8296 -> 8272 bytes 08-build_abe-glibc/console.log.xz | Bin 239592 -> 240252 bytes 09-build_abe-stage2/console.log.xz | Bin 203216 -> 203856 bytes 10-build_abe-gdb/console.log.xz | Bin 37512 -> 37704 bytes 11-build_abe-qemu/console.log.xz | Bin 31296 -> 31700 bytes 12-check_regression/console.log.xz | Bin 3700 -> 3784 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++-------- 19 files changed, 55 insertions(+), 55 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_tx1/llvm-master-aarch64-spec2k6-O3 updated (b645cdcf72 -> 3ecdb0ee21)

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_llvm_tx1/llvm-master-aarch64-spec2k6-O3 in repository toolchain/ci/base-artifacts. from b645cdcf72 0: init: #475: 1: [TCWG CI] No change after baseline build: [...] new 3ecdb0ee21 1: onsuccess: #477: 1: [TCWG CI] 456.hmmer built and run OK [...] 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 1728 -> 1828 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 32248 -> 30392 bytes 04-build_abe-stage1/console.log.xz | Bin 74908 -> 73052 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9208 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 240384 -> 239980 bytes 08-build_abe-stage2/console.log.xz | Bin 185016 -> 176568 bytes 09-build_llvm-true/console.log.xz | Bin 62792 -> 63204 bytes 10-benchmark/benchmark-build.log | 116 +- 10-benchmark/benchmark.log | 114 +- 10-benchmark/console.log.xz | Bin 4020 -> 4080 bytes 11-check_regression/console.log.xz | Bin 9260 -> 12464 bytes 11-check_regression/csv-results-0/md5sum.csv | 780 +- 11-check_regression/csv-results-0/results.csv | 268206 +++++++++--------- 11-check_regression/csv-results-0/size.csv | 264544 ++++++++--------- 11-check_regression/csv-results-0/vect.csv | 18974 +- 11-check_regression/csv-results-1/md5sum.csv | 1631 +- 11-check_regression/csv-results-1/perf.csv | 1958 +- 11-check_regression/csv-results-1/results.csv | 247263 ++++++++-------- 11-check_regression/csv-results-1/size.csv | 258978 +++++++++-------- 11-check_regression/csv-results-1/vect.csv | 19683 +- 11-check_regression/exe.improvement | 2 + 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 4 + 11-check_regression/mail-body.txt | 4 + 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-brief.csv | 34 +- 11-check_regression/results-compare.csv | 8 +- 11-check_regression/results-full.csv | 1869 +- 11-check_regression/results-internal.csv | 139 +- 11-check_regression/results.csv | 139 +- 11-check_regression/results.log | 888 +- 12-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 16 +- dashboard/squad/400.perlbench/results-metrics.json | 4 +- dashboard/squad/401.bzip2/results-functional.json | 4 +- dashboard/squad/401.bzip2/results-metadata.json | 16 +- dashboard/squad/401.bzip2/results-metrics.json | 3 + dashboard/squad/403.gcc/results-metadata.json | 16 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 16 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 16 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 16 +- dashboard/squad/447.dealII/results-metadata.json | 16 +- dashboard/squad/447.dealII/results-metrics.json | 4 +- dashboard/squad/450.soplex/results-metadata.json | 16 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 16 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-functional.json | 4 +- dashboard/squad/456.hmmer/results-metadata.json | 16 +- dashboard/squad/456.hmmer/results-metrics.json | 3 + dashboard/squad/458.sjeng/results-metadata.json | 16 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 16 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 16 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 16 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 16 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 16 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 16 +- dashboard/squad/483.xalancbmk/results-metrics.json | 4 +- dashboard/squad/Mean/results-metadata.json | 16 +- dashboard/squad/Mean/results-metrics.json | 6 +- dashboard/squad/dashboard-push-squad.sh | 74 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 30 +- mail/mail-body.txt | 30 +- mail/mail-subject.txt | 2 +- manifest.sh | 39 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1287868 -> 1286192 bytes save-temps/401.bzip2.tar.xz | Bin 0 -> 110632 bytes save-temps/403.gcc.tar.xz | Bin 3598228 -> 3611472 bytes save-temps/429.mcf.tar.xz | Bin 35044 -> 35076 bytes save-temps/444.namd.tar.xz | Bin 199116 -> 199100 bytes save-temps/445.gobmk.tar.xz | Bin 2087860 -> 2073552 bytes save-temps/447.dealII.tar.xz | Bin 3628036 -> 3563836 bytes save-temps/450.soplex.tar.xz | Bin 543320 -> 551328 bytes save-temps/453.povray.tar.xz | Bin 1256148 -> 1246812 bytes save-temps/456.hmmer.tar.xz | Bin 0 -> 366304 bytes save-temps/458.sjeng.tar.xz | Bin 161944 -> 162760 bytes save-temps/462.libquantum.tar.xz | Bin 56992 -> 56540 bytes save-temps/470.lbm.tar.xz | Bin 26156 -> 26156 bytes save-temps/471.omnetpp.tar.xz | Bin 830652 -> 839700 bytes save-temps/473.astar.tar.xz | Bin 80656 -> 80036 bytes save-temps/482.sphinx3.tar.xz | Bin 248560 -> 248348 bytes save-temps/483.xalancbmk.tar.xz | Bin 7304860 -> 7427528 bytes 99 files changed, 540202 insertions(+), 545667 deletions(-) create mode 100644 11-check_regression/exe.improvement create mode 100644 save-temps/401.bzip2.tar.xz create mode 100644 save-temps/456.hmmer.tar.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (9aafb50044 -> 18bdaecc1f)

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/master-aarch64 in repository toolchain/ci/base-artifacts. discards 9aafb50044 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards ad84996055 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 701106d877 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 7ff79b3f3b 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards 856a06fd55 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards a9d3ede90b 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards 2a43b4520f 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards c3cbb7df87 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards 2e1634aa47 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards cb69b289ae 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards cc40e23a99 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards adf8632700 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards a6299e502e 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards fa383f7b21 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards 1d2aa62940 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards b5ec6fb075 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 3641e7ee92 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 45a67d78a4 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards f91c32c08d 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards 5b3184836e 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 532728605a 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards f7cad6d3e1 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 1e9ec2bc84 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards e2d3aa601f 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 83275dfa95 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 72cd88f906 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 3e8f0e7885 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards 1a402f0f0e 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards 1dfb02450b 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 77d8c67154 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 7e32f27b22 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards e7027ecae8 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 0ed3b76bb8 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 6e19c87f3b 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 3a0fb0e6d1 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 900721f7c9 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards 9646aa2691 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 5584426068 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 7507941741 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards ec95747c40 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 938c679448 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 108501b80a 91: onsuccess: 1: Success after gcc: Daily bump. discards c837f9a1e9 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 5de481ee17 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 8e8e9f5875 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 5287f1f097 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 6ddda75ad6 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 14285a65fe 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards a64e7bcec7 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 9a5dad6ff4 83: onsuccess: 1: Success after gcc: 8 commits discards e3986317de 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 8cd77f27ad 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards 2971010a7c 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards d2e8c515fa 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 8d121e7f3f 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 78027d9723 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 253d6ef3f9 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards ec63742c6e 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards c8316bf7a0 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards cc980d0e51 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards e613bcdce8 72: onsuccess: 1: Successful build after gcc: 2 commits discards 08292b3ea4 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 5c25d2a4b9 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 6f875dd98a 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards a0ae586967 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 30254ffad0 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards b8a4c9bf98 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards e6df5b7c8c 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 6deca15d24 64: onsuccess: 1: Successful build after gcc: 5 commits discards d245f5831f 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards c694f49e05 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards df928c97a3 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards ce24bc99f3 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards abab82dcb5 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 3cc84c9344 58: onsuccess: 1: Successful build after binutils: 2 commits discards 5196e6bf06 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards c757e437fb 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 6be7154779 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards f1ae5493b7 54: onsuccess: 1: Successful build after gcc: 7 commits discards d2f4aca919 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards f79d2b2a13 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 969f3dae3e 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 87fb1ffbb8 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 45d91f61f9 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 4da3ee0e99 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 6b00cca937 47: onsuccess: 1: Successful build after binutils: 2 commits discards c911dc3539 46: onsuccess: 1: Successful build after gcc: Daily bump. discards 7c4943b8eb 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards e341fe5e7a 44: onsuccess: 1: Successful build after gcc: 2 commits discards 89cd80ba44 43: onsuccess: 1: Successful build after gcc: Daily bump. discards 8fdee14770 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards af853e450a 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards cc944a7e76 40: onsuccess: 1: Successful build after gcc: 2 commits discards 40800b8365 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 36ce75719e 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 8e155eb975 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 9b22ca54ee 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 2f7aa90dc8 35: onsuccess: 1: Successful build after gcc: 4 commits discards 500ff9a43c 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards a45ed99c4b 33: onsuccess: 1: Successful build after gcc: 10 commits discards cf99193fb8 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits new f3c697239f 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits new c3a4670554 33: onsuccess: 1: Successful build after gcc: 10 commits new b46a63f73b 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits new cc1d79efcd 35: onsuccess: 1: Successful build after gcc: 4 commits new 501de2e2ae 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 5fe8e00064 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 14298c4ac9 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 44f359b103 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new e284a1b401 40: onsuccess: 1: Successful build after gcc: 2 commits new 1a65ee5cab 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 4c6c2a5614 42: onsuccess: 1: Successful build after binutils: Automatic [...] new f91cd5424a 43: onsuccess: 1: Successful build after gcc: Daily bump. new 3334ea7850 44: onsuccess: 1: Successful build after gcc: 2 commits new 396bb3fe38 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new c53db79129 46: onsuccess: 1: Successful build after gcc: Daily bump. new 19df80e978 47: onsuccess: 1: Successful build after binutils: 2 commits new 515cf01155 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new bdaa6f0bc0 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new be73cda9ee 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 3c4f3618d5 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new feb12ae60d 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 4ccb5228cc 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 26cad157b2 54: onsuccess: 1: Successful build after gcc: 7 commits new 5826a5eb75 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new b23b40d2d0 56: onsuccess: 1: Successful build after gcc: Daily bump. new 83e7b894b4 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 0c49366853 58: onsuccess: 1: Successful build after binutils: 2 commits new f6ec970783 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new cf9e715413 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d7a8023b7d 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 3c80a63c70 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new f201115604 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new de5dbb9944 64: onsuccess: 1: Successful build after gcc: 5 commits new 6c224debc2 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new d13b0a5df5 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 2cdeab99e6 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new fdedaab4d6 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 7cbd00983d 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 9dc1914dae 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 320e810966 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new c75286e7db 72: onsuccess: 1: Successful build after gcc: 2 commits new 7d5e85f2b9 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 8196a0faa1 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 25ed4f442d 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new b17002d23d 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 25a3817881 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 9f4a7d8139 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 7d89ecb27e 79: onsuccess: 1: Successful build after gcc: Daily bump. new 58ba8562d7 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 1791a103b2 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 2e37a9bbc6 82: onsuccess: 1: Success after binutils/gcc: 10 commits new dc5f9ccfcd 83: onsuccess: 1: Success after gcc: 8 commits new cb326fc555 84: onsuccess: 1: Success after binutils/gcc: 9 commits new be6e408982 85: onsuccess: 1: Success after binutils/gcc: 9 commits new 4ff1dfcfed 86: onsuccess: 1: Success after binutils/gcc: 13 commits new 9562ea5ba4 87: onsuccess: 1: Success after binutils/gcc: 4 commits new 64b9e37195 88: onsuccess: 1: Success after binutils/gcc: 16 commits new f266cd46e2 89: onsuccess: 1: Success after binutils/gcc: 9 commits new a478490e18 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 95549e2e9a 91: onsuccess: 1: Success after gcc: Daily bump. new f9ee9d6d91 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 0744a67afc 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 1b5a3adbaa 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 60a3df4be7 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new 31853eb09a 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 23c0c9061b 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 5f2feafe02 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 295b4d3c27 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 2ea29bd907 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 90e56295bd 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new e8fadc5bec 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 92e622aaed 103: onsuccess: #2020: 1: Success after gcc: 2 commits new a27e413f31 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 45b329f064 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 4774af4275 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 6f4c7a0c30 107: onsuccess: #2024: 1: Success after gcc: 3 commits new f4e49a3e2b 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 83bd729237 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 71e5f8c26c 110: onsuccess: #2027: 1: Success after gcc: 5 commits new 354fd64538 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new b2da9e6bac 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new cc2818c135 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 21bfd772bb 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new a8f500d0be 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new a5eb9b2a92 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new ac1b9e1f86 117: onsuccess: #2034: 1: Success after binutils: 2 commits new d72b12f072 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 99dbba43dc 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new 346d2441eb 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new 4ee75c7984 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new b2ed747758 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new 4e69759838 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 23426f12e4 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new 7aeed6394a 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 2338eff922 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new 9aac5d00b5 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 6753a23190 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new ffd562e796 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 3587eaefb6 130: onsuccess: #2049: 1: Success after gcc: 9 commits new 7e6aaf9150 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new 90395d9849 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 18bdaecc1f 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 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 (9aafb50044) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1756 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 38324 -> 38040 bytes 04-build_abe-gcc/console.log.xz | Bin 214740 -> 212284 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2732 -> 2624 bytes 07-check_regression/console.log.xz | Bin 4752 -> 4932 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 30 +- 08-update_baseline/console.log | 36 +- 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 +- sumfiles/g++.log.xz | Bin 3577360 -> 3578780 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 3109596 -> 3092912 bytes sumfiles/gcc.sum | 4816 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1042660 -> 1034880 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2180 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207368 -> 207460 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2540 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 446168 -> 444924 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2583 insertions(+), 2555 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_ubsan updated (8cd9dfbcc8 -> e9c27c4b24)

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-aarch64-bootstrap_ubsan in repository toolchain/ci/base-artifacts. from 8cd9dfbcc8 43: onsuccess: #466: 2: Success after binutils/gcc: 4 commits new e9c27c4b24 44: onsuccess: #467: 2: Success after binutils/gcc: 41 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 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38076 -> 38004 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 325992 -> 326280 bytes 06-check_regression/console.log.xz | Bin 2700 -> 3100 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_lto updated (273bcd5d1d -> 0cf18a80ca)

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_lto in repository toolchain/ci/base-artifacts. from 273bcd5d1d 45: onsuccess: #451: 2: Success after binutils/gcc: 4 commits new 0cf18a80ca 46: onsuccess: #452: 2: Success after binutils/gcc: 42 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 1680 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50592 -> 50480 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 473204 -> 471980 bytes 06-check_regression/console.log.xz | Bin 2676 -> 3136 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 | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022