Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[gcc] branch releases/gcc-11 updated (02646956ec8 -> c4f53f59aaa)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 02646956ec8 Daily bump. new 6a552015b9c Fortran: improve error recovery while simplifying size of b [...] new 0a4fff071ff Fortran: NULL pointer dereference in invalid simplification [...] new 8a24700c64c Fortran: fix ICE in generate_coarray_sym_init [PR82868] new c4f53f59aaa Fortran: error recovery while simplifying intrinsic UNPACK [...] 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/fortran/expr.c | 3 ++- gcc/fortran/simplify.c | 18 +++++++++++++----- gcc/fortran/trans-decl.c | 1 + .../{associate_26.f90 => associate_26a.f90} | 6 +++--- gcc/testsuite/gfortran.dg/pr103694.f90 | 11 +++++++++++ gcc/testsuite/gfortran.dg/pr106985.f90 | 8 ++++++++ gcc/testsuite/gfortran.dg/pr107054.f90 | 13 +++++++++++++ 7 files changed, 51 insertions(+), 9 deletions(-) copy gcc/testsuite/gfortran.dg/{associate_26.f90 => associate_26a.f90} (65%) create mode 100644 gcc/testsuite/gfortran.dg/pr103694.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr106985.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr107054.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch releases/gcc-10 updated (a0009aba8ed -> b2bd7622721)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from a0009aba8ed Daily bump. new c59d1e73a61 Fortran: improve error recovery while simplifying size of b [...] new 12cd4a7c465 Fortran: NULL pointer dereference in invalid simplification [...] new f2509f61958 Fortran: fix ICE in generate_coarray_sym_init [PR82868] new b2bd7622721 Fortran: error recovery while simplifying intrinsic UNPACK [...] 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/fortran/expr.c | 3 ++- gcc/fortran/simplify.c | 18 +++++++++++++----- gcc/fortran/trans-decl.c | 1 + .../{associate_26.f90 => associate_26a.f90} | 6 +++--- gcc/testsuite/gfortran.dg/pr103694.f90 | 11 +++++++++++ gcc/testsuite/gfortran.dg/pr106985.f90 | 8 ++++++++ gcc/testsuite/gfortran.dg/pr107054.f90 | 13 +++++++++++++ 7 files changed, 51 insertions(+), 9 deletions(-) copy gcc/testsuite/gfortran.dg/{associate_26.f90 => associate_26a.f90} (65%) create mode 100644 gcc/testsuite/gfortran.dg/pr103694.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr106985.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr107054.f90 -- 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 (570ce02f4b -> 5ff743c5b3)

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 570ce02f4b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 52df9a66f1 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 4e176eaf40 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 62d6233a8d 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 04170bf518 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 46f65a82ce 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards f0ade27006 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards bfd16e44d9 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 59e16aafb8 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards da000130be 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 3e15bd5fb6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 4efd64c9c7 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 232b85ceba 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 289cb3277c 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 2e1c24e86b 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 957ba58bf8 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards e5f1682e4d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 85d0a03403 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards b9f3d97bd4 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards c604a8d9a4 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards dc53777d86 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards c4f369d8d0 128: onsuccess: #1723: 1: Success after linux: 12 commits discards e60a4cfebf 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 66260b16de 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 62c140a10a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards feda6cced5 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards f9dd369e53 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 2232942f49 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 5adf637d7d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 80033c4968 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 7652f7a4d9 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 18bf013f30 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b3b06a00d4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards beaff14e73 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards a4099feeae 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 507908ffa8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards d642121417 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 9dc1dda699 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 1744358d53 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 40d864c120 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 3f5589016e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 62d009622b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 8091b72ed2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9f18136107 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards bcaafceae8 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards d478bc10d7 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards aa1359c8b7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 246335503e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 54012e09d7 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 61ad149cb8 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards d344d64a8d 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 3ded6c973a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f81b0af170 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 8e83b96aa2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 444f3b2cfb 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 05f7a6540c 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 37a3fab4c4 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c25b899e02 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 10de729902 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards a87a196cb6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a598665c09 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards cf163926a9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2d6e809b4c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 33a47a017c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 71dbee2fc1 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 78943fc972 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 867899a3e1 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards f2cc2b45d3 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e785018eb7 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a794195b4c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards b465e2b288 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards fff0b9ac74 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 26e10ff634 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0c3ad31c28 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards e005d35fab 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 05ab332e63 74: onsuccess: 1: Successful build after linux: 44 commits discards e7be8be677 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 84f7d183c1 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 558bf1f7ac 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards ee34af6070 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 6f516485d0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards bda6c7d34c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1effdfe09e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0d0ea56fa2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7c379500cd 65: onsuccess: 1: Successful build after gcc: 4 commits discards 6d5f2c5bd4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b60cbd9823 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e5f9c9136d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 925de18f72 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3fbb992695 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 01d5b85d3a 59: onsuccess: 1: Successful build after glibc: 2 commits discards 17246d152c 58: onsuccess: 1: Successful build after binutils: 2 commits discards fd98804f7a 57: onsuccess: 1: Successful build after gcc: 7 commits discards 839729bad9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bb994f7db3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 043c2aafea 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards ca75dc5008 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 384a44745f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards b33ab3a079 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b627aaa175 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 21dda0fc6f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 87fd059afc 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b34a4ff93c 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6c4851d9c5 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 00099e56ea 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 59c29b850a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0c6fd883a5 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 2fffe0681f 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb06c17286 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 818bba84e3 57: onsuccess: 1: Successful build after gcc: 7 commits new a0ab07e12f 58: onsuccess: 1: Successful build after binutils: 2 commits new 51e36cc1bd 59: onsuccess: 1: Successful build after glibc: 2 commits new e074ff7971 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 835d31095d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new dc85d10525 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new bddac867c7 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 51b2bf706c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 642609f3c6 65: onsuccess: 1: Successful build after gcc: 4 commits new 564cd633ed 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8b9fb74467 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cc1bb61150 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6958d48eca 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 6ceecb7518 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 59b01a7130 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new b5aaf16e02 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2b20b42ad 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new afc0e77016 74: onsuccess: 1: Successful build after linux: 44 commits new 2d15305894 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aa4a4f9eda 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 6ddc1c5fc3 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d5ff1c9d97 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 54d07d776e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6fc45e3aa3 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new e6bd18213c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 2933b505b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 8fe15a0c0c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 90e0996b88 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 26bd683491 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 63da97653a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new ab1b248fdb 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 2e25d0c796 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 79154a537c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b372f347f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new de72ecea99 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new f47b979cbc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 88c1b85c0e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c48b015212 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 193935ddb9 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new c3fb8eaba5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new d37f0b758c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 33b39abf66 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new d2b827105f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new cff1b9c2f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 2eb5875d9e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 9db737ff43 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new f292704a0f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new e51dce9c94 104: onsuccess: #1697: 1: Success after gcc: 4 commits new ecda3331fd 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new c0fd022f11 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 6fdbc67ca5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 6cd8175017 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 92af2765eb 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 07dc331bec 110: onsuccess: #1703: 1: Success after gcc: 6 commits new ab2848b45c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 1639a573d7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 7a4c8af082 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 65c40aea67 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 73096b6c9a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 99e70b99d1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 7c7e41e0c9 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new a6e086d4f8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new e9d6b24a7c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new f6499222e1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new b153967597 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 7b1e4c33bb 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 0176eb0cab 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 5d8d8d8b1d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 1ab787969e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new efdc0c5110 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new de9111dd1a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6dca6aaacb 128: onsuccess: #1723: 1: Success after linux: 12 commits new 6b0db4273c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new c8163e6e46 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new e57bff34f6 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 1403e301ba 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 91eec19290 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new c9da380fd6 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 793b025dc5 135: onsuccess: #1733: 1: Success after binutils: 5 commits new d05b4eaca9 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 0095cbf25f 137: onsuccess: #1736: 1: Success after gcc: 5 commits new bb829aac99 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new f2b648fb9d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 5f5063c716 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 2a722f4fca 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 054b1d2182 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 30313766d4 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 5d927d71c6 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 7d001a576d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 45da3cd9b8 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 7f1fcb1aa4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new b89ad94942 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new c4f36cb77c 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 5ff743c5b3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (570ce02f4b) \ 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 1732 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29912 -> 30156 bytes 04-build_abe-stage1/console.log.xz | Bin 91120 -> 91196 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8464 -> 8676 bytes 07-build_abe-glibc/console.log.xz | Bin 233632 -> 233600 bytes 08-build_abe-stage2/console.log.xz | Bin 223696 -> 225056 bytes 09-build_abe-gdb/console.log.xz | Bin 37252 -> 37416 bytes 10-build_abe-qemu/console.log.xz | Bin 31988 -> 31468 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3156 -> 3148 bytes 13-check_regression/console.log.xz | Bin 6496 -> 7736 bytes 13-check_regression/fails.sum | 3 +- 13-check_regression/mail-body.txt | 65 +- 13-check_regression/results.compare | 39 +- 13-check_regression/results.compare2 | 268 +++- 13-check_regression/results.regressions | 39 +- 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 67 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 39 +- sumfiles/g++.log.xz | Bin 2694152 -> 2658932 bytes sumfiles/g++.sum | 266 ++-- sumfiles/gcc.log.xz | Bin 2209208 -> 2203868 bytes sumfiles/gcc.sum | 2394 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 880904 -> 887140 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201412 -> 201608 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 425084 -> 429464 bytes sumfiles/libstdc++.sum | 23 +- 44 files changed, 1878 insertions(+), 1497 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (61786edf7a8 -> 7069d03ba4a)

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 61786edf7a8 arm, csky: Fix C++ ICEs with _Float16 and __fp16 [PR107080] new 7069d03ba4a libstdc++: Fix broken dg-prune-output 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: libstdc++-v3/testsuite/20_util/bind/ref_neg.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 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_build/master-arm updated (e514d07682 -> 80815acba3)

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 e514d07682 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 068ba79527 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards 065b36b7bf 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 3f828e3c21 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 5919cae3a7 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards e18d9c2074 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 313315b69b 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 830441d135 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 258a03de2b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 18f6c7c0b2 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 5b770f7de5 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 8815e8c20e 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 95004054df 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 1ce24dfdba 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards a8ed850e08 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards ee5ee2b355 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 85d71ca1de 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards dade1915db 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 99da78d9ab 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards f3d3938413 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards a81d900f65 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 918d8c17f2 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 0868ee2e90 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 64594196e9 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 433004a0f7 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards ff19260914 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 3ef077ab60 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards daea0ec246 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 6aaee169dd 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards ea81fc5db1 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 113691f8a0 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards dc0c2e42e2 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 63656b1866 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 2c2599aa98 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 9bb4877ca0 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 323c3ee87b 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 08c7a0aae0 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 0efdf4cb46 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 337f344f69 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 90049d123d 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 909ea7f256 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 9a9c014c39 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards ae383b6383 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 80f6a40674 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards deaedeb5d7 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 5b495eaeca 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 82a2c2ff3b 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 78df0cf1b5 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 897c3e12b9 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards c391e16528 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 9b89ecf76a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards a8ef7d27a3 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards b6eeb0c0db 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 54c5381310 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards d13ad8edd9 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 7ce1a6b5f5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 9529e3f7dc 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 51b833ec55 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 5f920633df 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 969273a753 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards b80f6c8fd9 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 63aa5b74ed 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards b67f7d213a 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7f8c122c66 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8aa1e239c1 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards af9a07e901 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards ec3c77c950 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 3c027b9cb7 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards e79afc6b7b 85: onsuccess: 7: Success after gcc: 9 commits discards 2680a09c67 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards fb18f8332e 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards b22be48b82 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards f6c6a151a5 81: onsuccess: 7: Successful build after gcc: 2 commits discards b65c76e55a 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 01660047b9 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards f571f97776 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 90c7ebef9e 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 49d223f6fc 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2cc0088fed 75: onsuccess: 7: Successful build after linux: 44 commits discards 2fc788ddfe 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 4116ef8d4c 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3111aacf0b 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards e9f3581f6d 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 741f672110 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards d6bbfafa0b 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 03c74ed2c0 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b32a16ac42 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 4f64d88022 66: onsuccess: 7: Successful build after gcc: 3 commits discards b19b0aa063 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 725014b541 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 627d77c4ac 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 2f7a271c11 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 198e09d311 61: onsuccess: 4: Successful build after gcc: 15 commits discards 5bf2693bcf 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards e15f665d1c 59: force: 7: Successful build after gcc: 2 commits discards ed6c27d200 58: onsuccess: 7: Successful build after glibc: 2 commits discards 5114a66362 57: onsuccess: 7: Successful build after gcc: 7 commits discards d12a77da9d 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 37319fb8d5 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8058d1e8b1 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 321f930f20 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new bc722f3478 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new bf2674a59a 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new e0e8e59e3c 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bb4a388229 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5f29e6db27 57: onsuccess: 7: Successful build after gcc: 7 commits new 8977414cb6 58: onsuccess: 7: Successful build after glibc: 2 commits new d3d82a3827 59: force: 7: Successful build after gcc: 2 commits new 5a07979d84 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 80e0f1bcc6 61: onsuccess: 4: Successful build after gcc: 15 commits new 9953efa9ba 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 6cdf83a575 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 9b7964e647 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 16b86f7eec 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new daacf134af 66: onsuccess: 7: Successful build after gcc: 3 commits new 4a31b3e1cb 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 53d26d96ee 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1d395c748c 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 10536ec21c 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new c5cd771cd7 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new f98025c1a1 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new fc2bd31069 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ce08152868 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 0a9fe88898 75: onsuccess: 7: Successful build after linux: 44 commits new 8df26a27e3 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a868337a79 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 195d34fdf9 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ed09bb3187 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 0da51ad775 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 2747549b5b 81: onsuccess: 7: Successful build after gcc: 2 commits new 0fb0bf7597 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 73651dc241 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new bb58dd4a4c 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 29e7a779ec 85: onsuccess: 7: Success after gcc: 9 commits new d956174fc6 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 60d4de58bc 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new f0ac4d8b5e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 5adbc4e110 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 220e6e4c4d 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9f893babc4 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d8b304d622 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 07e5699cc8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 7512e4f015 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 37060f2d30 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 3249b5e9b5 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new f97f205f9f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 493a7d144b 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 36652ef85b 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 701a863c59 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new fd9e01cbf1 101: onsuccess: #1609: 7: Success after binutils: 78 commits new d59641cd59 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new bc5f74a46c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new f38e0f8cc1 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 08e7d5057c 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 35c954685d 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 427ee4c7f1 107: onsuccess: #1618: 7: Success after gcc: 2 commits new c015873e69 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new ee6d802258 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new adbc7f7413 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 55efbe3cad 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 916d9b9108 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 46aa9b55c9 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 1aaf05fc9b 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new b75815ee22 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 0ca3fd587a 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 0775f8cfba 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 369ea1f47b 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 860d9ba816 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 1c0cf455a9 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new f5a9c524b0 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new 28860e8579 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new dc03947076 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new cb5a32d14d 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 055598dd1c 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 9dce4cd734 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new e41c249dfa 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 0314e1ad43 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new a7585dbf1d 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 689d4d38a1 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new bb3ee28e37 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 0ab9c4d392 132: onsuccess: #1645: 7: Success after linux: 23 commits new 704306dbc7 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new ac50e03bb8 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new da39b1e787 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new ff1216a3d7 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 68bc381268 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new d6da03761e 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 58e3a808c2 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 264a060d9d 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 3b8d33ab8e 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 3fe7371204 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 12ea6ddea8 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 276f2b2b3d 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 84a8cfef70 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 49892f617b 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 4406ffe4ee 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 9d394cd639 148: onsuccess: #1663: 7: Success after glibc: 2 commits new e64f218900 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new be3157cf8f 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new f955358f55 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 964d8b89de 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new c082faab18 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 80815acba3 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e514d07682) \ 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 1684 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 30424 -> 30148 bytes 05-build_abe-stage1/console.log.xz | Bin 91508 -> 91136 bytes 07-build_abe-linux/console.log.xz | Bin 8492 -> 8656 bytes 08-build_abe-glibc/console.log.xz | Bin 235636 -> 233736 bytes 09-build_abe-stage2/console.log.xz | Bin 225880 -> 224288 bytes 10-build_abe-gdb/console.log.xz | Bin 37120 -> 37476 bytes 11-build_abe-qemu/console.log.xz | Bin 31804 -> 31376 bytes 12-check_regression/console.log.xz | Bin 3996 -> 4488 bytes 13-update_baseline/console.log | 40 ++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +++++++++++++++++------------------ 21 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (b52b99b62df -> 61786edf7a8)

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 b52b99b62df diagnostics: Fix virtual location for -Wuninitialized [PR69543] new 61786edf7a8 arm, csky: Fix C++ ICEs with _Float16 and __fp16 [PR107080] 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/config/arm/arm.cc | 2 ++ gcc/config/csky/csky.cc | 10 +++++----- gcc/testsuite/g++.target/{aarch64 => arm}/pr107080.C | 2 +- 3 files changed, 8 insertions(+), 6 deletions(-) copy gcc/testsuite/g++.target/{aarch64 => arm}/pr107080.C (89%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch master updated (609c9d0951 -> ba70f69598)

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 glibc. from 609c9d0951 malloc: Do not clobber errno on __getrandom_nocancel (BZ #29624) new ba70f69598 Fix iseqsig for _FloatN and _FloatNx in C++ with GCC 13 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: math/math.h | 50 +++++++- math/test-math-iseqsig.cc | 290 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 339 insertions(+), 1 deletion(-) -- 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_build/master-aarch64 updated (225a878581 -> e19dc3d295)

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 225a878581 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 80da1edbf8 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards f721d4589c 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 619266d837 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards f57f6e4ba3 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 2694b60104 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 33db9b8662 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 89d0b07652 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards a787ecc3b6 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards c53af1cff9 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 9d86e74533 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 8f91d32148 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 154f79a91b 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 7f22da529e 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards a23300e194 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 8b80b585d3 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 723bbfa91c 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards e2ca10a67c 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards d4a6355848 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards e6c76975b6 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 96290f83a4 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards b5367e6a15 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 1c326f2c4a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 6a80ba9151 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 07d6503ae5 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards df54482cea 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards e2d4963647 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards e9460e4a38 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards d771789414 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards c7b46f8f80 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 5c63a13f0f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 74ae5a7b03 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards ce51c31dda 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 7a17ac0536 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 50a9f5c0fb 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 41c0301827 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 283f323f6e 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 25c0cc0ffd 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards daeb17442a 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards e3c9b76afb 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards fb8d1773cc 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 36dc374d65 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards f5d97171dc 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 904d9b419d 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 1598495f23 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 17b2eba8a8 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 7e380ef60f 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 7d3eaa41f2 102: force: #1551: 1: Failure after gcc: 306 commits discards 687894bf0c 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 7592b08b02 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 00383f5333 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 37b2f60dd2 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 04ccff08d6 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 6fc3facb8f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 40a05b5073 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6f4c68e528 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards f85b9c8514 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards a2ea1236d6 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards b5c6a51de3 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 9ec145d09a 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 9773caa7c4 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 315c272596 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 743d4acabc 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 2f40010745 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 0549c42662 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards fb3525eb9c 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6d71b70cb1 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cbf062ed08 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 85529a4cb9 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 333a7abb9e 80: onsuccess: 7: Successful build after linux: 44 commits discards f98d714770 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c630148cfd 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards d3c4c75fd6 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 446b072115 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 0d6b57e3c6 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 66e4a4fc93 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ce5607d6f2 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7df2a78c9c 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 130566037a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2c949ccb50 70: onsuccess: 7: Successful build after gcc: 4 commits discards 3e0de6c593 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 94c868f14e 68: onsuccess: 7: Successful build after linux: 6 commits discards 7d7a2593e8 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 957c3233d0 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 504dd2b02f 65: onsuccess: 7: Successful build after binutils: 3 commits discards b9d4e7b7bb 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 1e65a73396 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards ef360ae470 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4ba9d5fa44 61: onsuccess: 4: Successful build after gcc: 5 commits discards 534d944432 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards f1a8c82151 59: force: 7: Successful build after gcc: 3 commits discards e9066dd907 58: onsuccess: 7: Successful build after glibc: 2 commits discards b4de426809 57: onsuccess: 7: Successful build after gcc: 7 commits discards cf1be0130e 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9fec548da7 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0a12db3fb2 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards a6f9a331a3 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards c1de2774f7 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 53efb95d2b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 10d6f26a90 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1d7d382c48 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 87bf64b6e7 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 39bba0e279 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 123b90c766 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a79b17200a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new b21ae178c0 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 824ce943c3 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new e3bc225115 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2278b88f0f 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 17c279db1e 57: onsuccess: 7: Successful build after gcc: 7 commits new 7aa5a5cf2d 58: onsuccess: 7: Successful build after glibc: 2 commits new d3b0621f15 59: force: 7: Successful build after gcc: 3 commits new 5a32f5167e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 6492a3a9b9 61: onsuccess: 4: Successful build after gcc: 5 commits new 37abe245d4 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 1fc5772a04 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new f3cef8d6ab 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 2138e19228 65: onsuccess: 7: Successful build after binutils: 3 commits new a35f01138e 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 56310234dc 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 891348c50a 68: onsuccess: 7: Successful build after linux: 6 commits new a85864339f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 52273cdc86 70: onsuccess: 7: Successful build after gcc: 4 commits new b0fe21063d 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new cca67bfb27 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 597d6e267f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e5cf0f6be3 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 69d1fbeaeb 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 8be3a73027 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new ebb7d1d870 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6f4cd10498 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 8f28027165 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 759e63b4f4 80: onsuccess: 7: Successful build after linux: 44 commits new 4db26b6cac 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new da58c21c6a 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 86abc121ca 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5288c73379 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 72050842db 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 316bde4182 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new f0463e5422 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 25c9b14dd5 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 1188a5032f 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 10faab4f4e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new e1527ec993 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 55c7430a45 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 66a66dd7b1 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 175392d033 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 47215ee23c 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9b9c8c488f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 58f75eaf48 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 9d53b1f4c5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new cfa4ed2f1e 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 2ed851d00b 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new a7b484a5e3 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 6eb14d96f2 102: force: #1551: 1: Failure after gcc: 306 commits new e10ad07e67 103: onsuccess: #1552: 1: Success after gcc: 5 commits new fe1872db29 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 6626fd9ab5 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 087c145baf 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new c220db1c74 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 4338f78beb 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new abd2fe3b78 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 4a29ea1fe5 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 34abed9c36 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 4f25974fc3 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 7a1434469a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 4eaa9f63c4 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 4d0a802fe0 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 66ee97dee1 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 90e8cebb1b 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new b935c1eb89 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new f1f3493ee2 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 6f275adfd2 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new aa8c73a2ab 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 42b6482aa3 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new eb77b36443 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 750c588471 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 6cf0b5a4aa 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 31eda81b71 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 9eb5dd02b9 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 93623b2000 128: onsuccess: #1579: 7: Success after linux: 12 commits new f4175f2140 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 875a917acb 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new fb5865ce69 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 2a15581337 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 78f8fcaa9a 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 6ec201adbb 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 729a91c88b 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new c4ecc7d5a3 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new e04a6fe2a0 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 4115fadad1 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 46f0eba61d 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 504d71d5df 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new dbfd26ee42 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new c0491206dc 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 6b914a2ac4 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 9ff41cbf60 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 9c3f5c6c46 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new aad7879eb3 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 5c28a506e6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 76123cfe37 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new b4a9416e62 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new e19dc3d295 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (225a878581) \ 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 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30200 -> 30388 bytes 05-build_abe-stage1/console.log.xz | Bin 72740 -> 72780 bytes 07-build_abe-linux/console.log.xz | Bin 8460 -> 8656 bytes 08-build_abe-glibc/console.log.xz | Bin 239864 -> 239916 bytes 09-build_abe-stage2/console.log.xz | Bin 203060 -> 203196 bytes 10-build_abe-gdb/console.log.xz | Bin 37396 -> 37712 bytes 11-build_abe-qemu/console.log.xz | Bin 32160 -> 32012 bytes 12-check_regression/console.log.xz | Bin 3976 -> 4492 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 ++++++++++++------------ 21 files changed, 61 insertions(+), 61 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/master-aarch64 updated (edb036b732 -> 0245f5b940)

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 edb036b732 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits discards 2976d453e0 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits discards 9ca808ea80 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits discards f2454e15e1 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits discards 57c1f85115 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits discards 844ef94d65 141: onsuccess: #2073: 1: Success after binutils: 3 commits discards 7e09783be8 140: onsuccess: #2070: 1: Success after binutils: 4 commits discards 25c426b662 139: onsuccess: #2067: 1: Success after binutils: 2 commits discards 671a79a015 138: onsuccess: #2064: 1: Success after binutils: 4 commits discards 092b2000b5 137: onsuccess: #2061: 1: Success after binutils: 2 commits discards cf575d24c8 136: onsuccess: #2056: 1: Success after binutils: 4 commits discards 6df4a07a2f 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits discards 84f2708c0c 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits discards 03e40c2f92 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits discards 6bcf18cd14 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits discards 624b2b4b08 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] discards 8d68633a97 130: onsuccess: #2049: 1: Success after gcc: 9 commits discards 8dacca487e 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] discards a951db640d 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] discards 3c6efd77c0 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] discards d2aa8002fb 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] discards a17084416f 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits discards d56844b3c4 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits discards f826e9136b 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits discards 47aad657e1 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits discards 856cf016dc 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits discards 91f25648e5 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits discards 2e1173858b 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits discards c35abc8261 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits discards 0e7fcb4b6e 117: onsuccess: #2034: 1: Success after binutils: 2 commits discards 8b9fa3310b 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits discards 4e7bf1d8d8 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits discards 205aec77fa 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits discards df9f4b04f3 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits discards 253040233d 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits discards 7083a2bd4d 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits discards 8337a879ca 110: onsuccess: #2027: 1: Success after gcc: 5 commits discards 54ad8735b6 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits discards 25ae94ef27 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits discards 021cde3f21 107: onsuccess: #2024: 1: Success after gcc: 3 commits discards 40c841e2a9 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits discards d221a6b270 105: onsuccess: #2022: 1: Success after gcc: 4 commits discards faa9e4c6a1 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 5fb03d0245 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 32cfd23041 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] discards 40739cd869 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards ab1e1e3d0a 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 0af656e91e 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 9fd396cd04 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 23d1073513 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards a7ea01c9f9 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] discards 0e36f29960 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] discards 067f92fe58 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards 5d3ebe9568 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] discards 2f760d4dac 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards f6b3c4be14 91: onsuccess: 1: Success after gcc: Daily bump. discards 7ec65e0892 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards 3ade1f7626 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards b50801f729 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards a26bbaf752 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 0db189c584 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 3b34171edc 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 2240282645 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards fac1b158df 83: onsuccess: 1: Success after gcc: 8 commits discards d1d9e9f63e 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards b6b49743a3 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards c356081e10 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 4e63952e8f 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 2fc18aa27a 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards bb80db79bb 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 1af3450a20 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 4cab0d7cd2 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 65e896aba0 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 94bdf565cf 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards be7c231a29 72: onsuccess: 1: Successful build after gcc: 2 commits discards 92e4c6c6c1 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 00bd929440 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards a443bb1682 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 53890f84d1 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards cff7df920d 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 7ecf22ed6b 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards e3fd9f9108 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 354c1cef8e 64: onsuccess: 1: Successful build after gcc: 5 commits discards b5c1c3b5c6 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 0d36e47bd0 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 8a6d025b25 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards d2c94821be 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 8fc060b0a8 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 980c51e7d8 58: onsuccess: 1: Successful build after binutils: 2 commits discards da6c97f25d 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 28e4610633 56: onsuccess: 1: Successful build after gcc: Daily bump. discards 60870ba6dc 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 8dca8d6d62 54: onsuccess: 1: Successful build after gcc: 7 commits discards 932060cc36 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 06c2be07c7 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 42b016004e 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards ceec6ecd60 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 22ce3184ac 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 26b2ef2dd0 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 13e52f35e5 47: onsuccess: 1: Successful build after binutils: 2 commits discards 826c970905 46: onsuccess: 1: Successful build after gcc: Daily bump. new dc0d16b607 46: onsuccess: 1: Successful build after gcc: Daily bump. new d6dc381539 47: onsuccess: 1: Successful build after binutils: 2 commits new b4b7dc6c23 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 150d8ae495 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2d74dd024a 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 0f4bd42805 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 0ee1622cb0 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new caf8d614a6 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 67ceb5efe9 54: onsuccess: 1: Successful build after gcc: 7 commits new 82fa00cf95 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new 44bd07868a 56: onsuccess: 1: Successful build after gcc: Daily bump. new 942776107c 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new f8ab0c4cf6 58: onsuccess: 1: Successful build after binutils: 2 commits new ef0d3a9df7 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 4025e98625 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d01818ee5a 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 945dec2c17 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 3b995654aa 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new e7d560617b 64: onsuccess: 1: Successful build after gcc: 5 commits new e8f0913a18 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new eb3b06f541 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 21f9d3934d 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2d986c714d 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d7d07b65f0 69: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 02a6832d45 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 5be434af52 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new aae42926ff 72: onsuccess: 1: Successful build after gcc: 2 commits new 171f1b20c8 73: onsuccess: 1: Successful build after binutils: PR29494 T [...] new c5d23b454b 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 607151052f 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new e81e4e8dbc 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new d2c390a8e1 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 0aed564852 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 30725c132a 79: onsuccess: 1: Successful build after gcc: Daily bump. new df19e8aebe 80: onsuccess: 1: Success after binutils/gcc: 14 commits new a2f5371fbe 81: onsuccess: 1: Success after binutils/gcc: 27 commits new c707ed4176 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 482e87bed8 83: onsuccess: 1: Success after gcc: 8 commits new 934f08cd10 84: onsuccess: 1: Success after binutils/gcc: 9 commits new 353eab1763 85: onsuccess: 1: Success after binutils/gcc: 9 commits new dcdbcd1b8c 86: onsuccess: 1: Success after binutils/gcc: 13 commits new aebf1b9a72 87: onsuccess: 1: Success after binutils/gcc: 4 commits new a9f1b06207 88: onsuccess: 1: Success after binutils/gcc: 16 commits new ee237ca72e 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 94be438072 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 2e39b062db 91: onsuccess: 1: Success after gcc: Daily bump. new 7dbd27580c 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 516a5aaf68 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-239 [...] new 70c4d4b2e6 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new 823e1bca88 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-239 [...] new cc32c0cd90 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-239 [...] new 06274d3eaa 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 33f5bdc37b 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 337b22ec2a 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 3d9b1baa37 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new b4393c189a 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new b15840397b 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-27 [...] new 47bac0f8db 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 6ffed1b3f4 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 1a6ac37b4d 105: onsuccess: #2022: 1: Success after gcc: 4 commits new 2caef870a2 106: onsuccess: #2023: 1: Success after binutils/gcc: 3 commits new 1e7f5b1e96 107: onsuccess: #2024: 1: Success after gcc: 3 commits new 0332f92577 108: onsuccess: #2025: 1: Success after binutils/gcc: 2 commits new 895c2ddd34 109: onsuccess: #2026: 1: Success after binutils/gcc: 3 commits new 5564c2a986 110: onsuccess: #2027: 1: Success after gcc: 5 commits new f688bd788b 111: onsuccess: #2028: 1: Success after binutils/gcc: 8 commits new 0b637f0c21 112: onsuccess: #2029: 1: Success after binutils/gcc: 12 commits new a88af4cdbc 113: onsuccess: #2030: 1: Success after binutils/gcc: 15 commits new 5e5e94d98e 114: onsuccess: #2031: 1: Success after binutils/gcc: 7 commits new c29b38382e 115: onsuccess: #2032: 1: Success after binutils/gcc: 14 commits new a52b14b44b 116: onsuccess: #2033: 1: Success after binutils/gcc: 13 commits new e34f81be47 117: onsuccess: #2034: 1: Success after binutils: 2 commits new c2159c528b 118: onsuccess: #2035: 1: Success after binutils/gcc: 3 commits new 05ed307efc 119: onsuccess: #2036: 1: Success after binutils/gcc: 21 commits new ba57e9ab98 120: onsuccess: #2037: 1: Success after binutils/gcc: 24 commits new b92db78728 121: onsuccess: #2040: 1: Success after binutils/gcc: 37 commits new a6fe0775ba 122: onsuccess: #2041: 1: Success after binutils/gcc: 10 commits new bfa6dbcd8c 123: onsuccess: #2042: 1: Success after binutils/gcc: 3 commits new 9f2a0fa8da 124: onsuccess: #2043: 1: Success after binutils/gcc: 6 commits new e348a9fd1e 125: onsuccess: #2044: 1: Success after binutils/gcc: 3 commits new 8024204904 126: onsuccess: #2045: 1: Success after basepoints/gcc-13-28 [...] new da39a70be9 127: onsuccess: #2046: 1: Success after gdb-12-branchpoint-2 [...] new 8c2896a880 128: onsuccess: #2047: 1: Success after basepoints/gcc-13-28 [...] new c39112aec0 129: onsuccess: #2048: 1: Success after basepoints/gcc-13-28 [...] new 426033b851 130: onsuccess: #2049: 1: Success after gcc: 9 commits new f490cae700 131: onsuccess: #2050: 1: Success after gdb-12-branchpoint-2 [...] new cd43cf3812 132: onsuccess: #2051: 1: Success after binutils/gcc: 8 commits new 558307828b 133: onsuccess: #2052: 1: Success after binutils/gcc: 24 commits new 37d69e1129 134: onsuccess: #2053: 1: Success after binutils/gcc: 15 commits new 0c80aad71e 135: onsuccess: #2054: 1: Success after binutils/gcc: 7 commits new 6771819a32 136: onsuccess: #2056: 1: Success after binutils: 4 commits new 7ac4e8e774 137: onsuccess: #2061: 1: Success after binutils: 2 commits new c4367e06d0 138: onsuccess: #2064: 1: Success after binutils: 4 commits new 100210098d 139: onsuccess: #2067: 1: Success after binutils: 2 commits new 444b5a99c6 140: onsuccess: #2070: 1: Success after binutils: 4 commits new b11c22d008 141: onsuccess: #2073: 1: Success after binutils: 3 commits new 494f9b0791 142: onsuccess: #2075: 1: Success after binutils/gcc: 71 commits new 23b413592b 143: onsuccess: #2076: 1: Success after binutils/gcc: 14 commits new c02629ce5e 144: onsuccess: #2077: 1: Success after binutils/gcc: 15 commits new b2f8741424 145: onsuccess: #2078: 1: Success after binutils/gcc: 10 commits new 4953a5a29e 146: onsuccess: #2079: 1: Success after binutils/gcc: 14 commits new 0245f5b940 147: onsuccess: #2080: 1: Success after binutils/gcc: 13 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 (edb036b732) \ 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 1672 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 37572 -> 38356 bytes 04-build_abe-gcc/console.log.xz | Bin 211604 -> 214844 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3124 -> 3044 bytes 07-check_regression/console.log.xz | Bin 5388 -> 6100 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 6 + 07-check_regression/mail-body.txt | 26 + 07-check_regression/results.compare | 9 +- 07-check_regression/results.compare2 | 269 +- 07-check_regression/results.regressions | 26 + 08-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 26 + sumfiles/g++.log.xz | Bin 3575892 -> 3570724 bytes sumfiles/g++.sum | 153 +- sumfiles/gcc.log.xz | Bin 3095800 -> 3081880 bytes sumfiles/gcc.sum | 4578 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1043508 -> 1042684 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2184 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 207568 -> 207720 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2544 -> 2540 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 448256 -> 447304 bytes sumfiles/libstdc++.sum | 13 +- 36 files changed, 2792 insertions(+), 2419 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- 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_native_check_gcc/master-aarch64 updated (31c40b7046 -> b0f4193b0c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. from 31c40b7046 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new b0f4193b0c 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] 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 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2704 bytes 03-build_abe-binutils/console.log.xz | Bin 38260 -> 37980 bytes 04-build_abe-gcc/console.log.xz | Bin 212328 -> 211804 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9180 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 239508 -> 239368 bytes 08-build_abe-gdb/console.log.xz | Bin 37612 -> 37420 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3864 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2496 -> 3380 bytes 11-check_regression/console.log.xz | Bin 15012 -> 8088 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 22 +- 11-check_regression/mail-body.txt | 80 +- 11-check_regression/results.compare | 613 +--- 11-check_regression/results.compare2 | 1636 ++--------- 11-check_regression/results.regressions | 91 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 82 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 91 +- sumfiles/g++.log.xz | Bin 3712664 -> 3712476 bytes sumfiles/g++.sum | 186 +- sumfiles/gcc.log.xz | Bin 3245160 -> 3241876 bytes sumfiles/gcc.sum | 4878 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1077912 -> 1072756 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 220164 -> 219840 bytes sumfiles/libgomp.sum | 59 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451216 -> 448568 bytes sumfiles/libstdc++.sum | 19 +- 42 files changed, 3037 insertions(+), 4836 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page: