Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (0372fd3da42 -> 78a9e1023c7)

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 0372fd3da42 235: onsuccess: #1964: 7: Success after binutils/linux/glib [...] discards 502d72d1769 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 [...] discards bc657360ee4 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards 231e2f380ab 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/ [...] discards 3da07141dbb 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/ [...] discards 2b1961ca3b3 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/ [...] discards 2c5164cb897 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/ [...] discards 4eeb3d4bdb3 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards 040eaa57813 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards 53463af3593 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/ [...] discards 2301dad0c2a 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/ [...] discards 0bfbf47403d 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qe [...] discards ee634f964a1 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards 14519fb3132 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-4 [...] discards c63ac3cb51f 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...] discards 0d0a716fd53 220: force: #1948: 5: Success after gcc: 4 commits discards aa967be9667 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 440c505154e 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards 053c11971e5 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] discards fa631775743 216: onsuccess: #1940: 7: Success after linux: 12 commits discards 8158f986ae0 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards 366ab556601 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards 67454667fdd 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 28ea4ea7d67 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards 7e51d8bf9ab 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] discards 376be08c92b 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] discards 582810cc1ec 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] discards 4f07f404109 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 3150b8f9061 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] discards d84775f9ba8 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] discards 39ccf5b3cb5 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] discards 125c2cd7d56 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] discards d661a2c34a7 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] discards cc9c06b5bb5 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] discards 0e2a6bb9ffc 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] discards 5eea578dc1b 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] discards e762156e6b4 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] discards dab709ff7c0 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] discards 26509e70268 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] discards 07550e622c9 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 20c0625bf56 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] discards 006216073d7 194: force: #1853: 7: Success after gcc: 26 commits discards b6e987b6f09 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] discards 3129285b324 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 73e74c1515a 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 62b6d212783 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards e5c8899d7e2 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] discards 5ffdeab7149 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] discards 8e22279c250 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] discards f74527cb650 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] discards 7232fc880d0 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] discards a93a20e5197 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] discards 10635e896eb 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] discards de7d0f636ea 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] discards c9160f750f4 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] discards baa94ce75ea 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] discards 782ad218184 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] discards 54b1e5f7fd7 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] discards a3db69283ff 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] discards 645cc83330b 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] discards 12138285867 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] discards 85af21a9171 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] discards 077dad7c7a0 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] discards 89e266ad196 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 8d8745bca86 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] discards 178af78915f 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] discards bbf216b4791 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] discards e8e29eb45e6 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] discards 52e69030d0c 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 6cc73efda9f 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] discards 065c8b09da7 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] discards 4585307c3ad 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] discards 954f2f8bb76 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] discards 32e0a822fbb 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] discards 7554283465e 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] discards 402e84370fe 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] discards 3b39d69fd67 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] discards bc7d1111bee 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards ff14ebd5213 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards e4271e4e04f 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards cc1633b9dc3 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] discards 6f1ae23b30e 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] discards 89e2c8faff1 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] discards 9ebe9f2843a 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] discards 4c3aad64917 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] discards e89b448ac21 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] discards ba8cd385642 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] discards ca0eccd9cce 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards f3ed505903a 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] discards 21ff10ed70d 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] discards d55dba1d4aa 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] discards d136de1f2fc 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] discards bf0e783c572 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] discards 884aa729643 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] discards 2e4624c4b21 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards c99229f69a0 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] discards b0faaaeb847 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 1e4f7c1bfcf 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] discards a286774216d 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] discards bf6d1fdc8bf 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards d830538f6e8 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] new 832658f58da 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] new 969cdfb8919 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 64564a6a7e5 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] new 1cfc985858f 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] new 68b3696e457 139: onsuccess: #1654: 1: Success after gcc: 11 commits new bd19b2728fe 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] new a691e5c5378 141: onsuccess: #1656: 7: Success after gcc: 7 commits new ba3e4cd2ed8 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] new b755360f5b2 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] new 194f3bd3ad8 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] new 21933e39b9b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] new a1bcf30b235 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] new 23fcf2584f7 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] new 97ddffc396e 148: onsuccess: #1663: 7: Success after glibc: 2 commits new bc071cdde9d 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] new a43e9a4ca62 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] new e8e46fd95fd 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] new 3c183a1eb9d 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] new 1bf8ff19d32 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] new 14931363d8d 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] new 3778436dba6 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] new 56fc8a58451 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 0a18cde6f9d 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 0e2733b624d 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 25f0cdbb1ca 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] new 90ef2bb94c4 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] new 16844486f0f 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] new 2a5f532dc53 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] new 317a0f9f08a 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] new 3d8f662a654 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] new cf58986ad40 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] new 0c95ddc57c7 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] new 1c4151070de 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new b9348ea4b37 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] new 74e4ee7c702 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] new 93a461fda60 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] new c5ea4e77ebc 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] new b56e0ec20e8 172: onsuccess: #1687: 7: Success after gcc: 11 commits new c8850e8028f 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] new 81b519bb9d6 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] new 183fefc8371 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] new 6aeb12dd5b0 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] new a83446fba23 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] new c1c81cc923b 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] new 426ebca6966 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] new ac1112436a0 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] new 120b7f4cd29 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] new d525d0c6116 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] new 89978628dd9 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] new f6fb51d6bac 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] new 8fe15cb7cff 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] new 1e519395e55 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] new 2dbc2131b1a 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] new 25830bb74b0 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] new 0f6710177b4 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] new e0163cc00aa 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 087561269e4 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 87e8d5782bc 192: onsuccess: #1848: 7: Success after linux: 213 commits new b468a0b89ad 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] new 9c757eae272 194: force: #1853: 7: Success after gcc: 26 commits new 68f187fe7fa 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] new 15dd15fd470 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 74a15007ec3 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] new a66c82a9419 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] new 2a2194ec64b 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] new d9f5a871dde 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] new e61d48433ad 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] new 717013d6439 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] new 7df845bc0a6 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] new bdb30f98360 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] new 0a49a921c8d 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] new 0b88eeee69e 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] new 778b450ad98 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] new 27adc30b3ec 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new 235fe93b139 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] new 8ba58ff2c0f 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] new 7eee82b0167 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] new 95622f04cdd 212: onsuccess: #1934: 7: Success after gcc: 3 commits new f69b8dd9cac 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 919b29aa903 214: onsuccess: #1937: 7: Success after binutils: 4 commits new a2b08ba79ed 215: onsuccess: #1938: 7: Success after gcc: 4 commits new 6669fd4e867 216: onsuccess: #1940: 7: Success after linux: 12 commits new 8a89377132b 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] new 265dc8b0a15 218: onsuccess: #1943: 5: Success after gdb: 3 commits new a8cab851a79 219: onsuccess: #1945: 5: Success after binutils: 8 commits new 930b298d6ab 220: force: #1948: 5: Success after gcc: 4 commits new e31674de0c5 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...] new e90db310f13 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-4 [...] new 2646048626c 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new 4991f43cd0f 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qe [...] new 541a2a0db6f 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/ [...] new 4fb7b24e4f5 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/ [...] new 784e9ca7c97 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new 991c0997452 228: onsuccess: #1956: 7: Success after gcc: 5 commits new d3cc33b0303 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/ [...] new c9d00c0a1f7 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/ [...] new eac32497d1e 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/ [...] new 0b60c131806 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/ [...] new 3c68f19ca8c 233: onsuccess: #1962: 7: Success after gcc: 6 commits new 0e6f12c0f4c 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 [...] new ca95af51e21 235: onsuccess: #1964: 7: Success after binutils/linux/glib [...] new 78a9e1023c7 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 1 [...] 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 (0372fd3da42) \ 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 1732 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 32384 -> 32248 bytes 05-build_abe-stage1/console.log.xz | Bin 91820 -> 91956 bytes 07-build_abe-linux/console.log.xz | Bin 8628 -> 8728 bytes 08-build_abe-glibc/console.log.xz | Bin 237784 -> 236464 bytes 09-build_abe-stage2/console.log.xz | Bin 226940 -> 225860 bytes 10-build_abe-gdb/console.log.xz | Bin 39716 -> 39624 bytes 11-build_abe-qemu/console.log.xz | Bin 30712 -> 30512 bytes 12-check_regression/console.log.xz | Bin 4404 -> 3780 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ 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 | 34 +++++++++--------- 19 files changed, 58 insertions(+), 58 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/release-aarch64 updated (d576f0e3426 -> 38c92cf0d74)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/release-aarch64 in repository toolchain/ci/base-artifacts. from d576f0e3426 43: onsuccess: #152: 6: Success after binutils/gcc/linux/gd [...] new 38c92cf0d74 44: onsuccess: #153: 6: Success after binutils/gcc/linux/gd [...] 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 1720 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 38692 -> 38548 bytes 05-build_abe-gcc/console.log.xz | Bin 207060 -> 208248 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8660 -> 8816 bytes 08-build_abe-glibc/console.log.xz | Bin 240504 -> 243124 bytes 09-build_abe-gdb/console.log.xz | Bin 37356 -> 37844 bytes 10-check_regression/console.log.xz | Bin 3800 -> 3896 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++++----------------- 18 files changed, 25 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (ea4b23d9c82 -> 7676235f690)

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 ea4b23d9c82 libgomp: Handle OpenMP's reverse offloads new 7676235f690 ivopts: Fix IP_END handling for asm goto [PR107997] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.c-torture/compile/pr107997.c | 23 +++++++++++++++++++++++ gcc/tree-ssa-loop-ivopts.cc | 7 +++++++ 2 files changed, 30 insertions(+) create mode 100644 gcc/testsuite/gcc.c-torture/compile/pr107997.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (b813665fd2e -> 823b2395e44)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from b813665fd2e Automatic date update in version.in new 823b2395e44 [gdb/tdep] Fix larl handling in s390_displaced_step_fixup The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/s390-tdep.c | 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, 5 months

[gcc] branch master updated (68ee8a64ac1 -> ea4b23d9c82)

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 68ee8a64ac1 Add initial ChangeLogs for modula2. new ea4b23d9c82 libgomp: Handle OpenMP's reverse offloads 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: libgomp/libgomp.h | 77 ++- libgomp/oacc-host.c | 1 + libgomp/plugin/plugin-nvptx.c | 4 +- libgomp/splay-tree.c | 22 + libgomp/splay-tree.h | 8 + libgomp/target.c | 599 ++++++++++++++++++++- .../libgomp.fortran/reverse-offload-2.f90 | 72 +++ .../libgomp.fortran/reverse-offload-3.f90 | 68 +++ .../libgomp.fortran/reverse-offload-4.f90 | 129 +++++ .../libgomp.fortran/reverse-offload-5.f90 | 100 ++++ .../libgomp.fortran/reverse-offload-5a.f90 | 98 ++++ 11 files changed, 1139 insertions(+), 39 deletions(-) create mode 100644 libgomp/testsuite/libgomp.fortran/reverse-offload-2.f90 create mode 100644 libgomp/testsuite/libgomp.fortran/reverse-offload-3.f90 create mode 100644 libgomp/testsuite/libgomp.fortran/reverse-offload-4.f90 create mode 100644 libgomp/testsuite/libgomp.fortran/reverse-offload-5.f90 create mode 100644 libgomp/testsuite/libgomp.fortran/reverse-offload-5a.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch devel/modula-2 updated (4487e05a7c4 -> d90b603b6b8)

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/modula-2 in repository gcc. from 4487e05a7c4 Alphabetically order options in gm2.texi and lang.opt and p [...] new d90b603b6b8 Purged out of gcc tree info from the documentation. 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/doc/gm2.texi | 171 ++++++++++++------------------------------------------- 1 file changed, 35 insertions(+), 136 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (24ff0b3e0c4 -> 68ee8a64ac1)

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 24ff0b3e0c4 Add stub 'gcc/rust/ChangeLog' new 68ee8a64ac1 Add initial ChangeLogs for modula2. 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/{rust => m2}/ChangeLog | 1 - {gcc/rust => libgm2}/ChangeLog | 1 - 2 files changed, 2 deletions(-) copy gcc/{rust => m2}/ChangeLog (99%) copy {gcc/rust => libgm2}/ChangeLog (99%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch users/ibhagat/try-libctf-build-v2 created (now 5ef8f1caa53)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch users/ibhagat/try-libctf-build-v2 in repository binutils-gdb. at 5ef8f1caa53 libctf: remove unnecessary zstd constructs This branch includes the following new commits: new 96a87e6aa06 libctf: remove unnecessary zlib constructs new 9f72b0c1673 libctf: remove AC_CONFIG_MACRO_DIR new 5ef8f1caa53 libctf: remove unnecessary zstd constructs The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (325529e21e8 -> 24ff0b3e0c4)

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 325529e21e8 Prepare 'contrib/gcc-changelog/git_commit.py' for GCC/Rust new 84f6f8a2a97 Fortran: Replace simple '.' quotes by %<.%> new 24ff0b3e0c4 Add stub 'gcc/rust/ChangeLog' The 2 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/match.cc | 2 +- gcc/fortran/openmp.cc | 38 ++++++++++++++--------------- gcc/fortran/primary.cc | 6 ++--- gcc/fortran/resolve.cc | 10 ++++---- include/ChangeLog.jit => gcc/rust/ChangeLog | 7 +----- 5 files changed, 29 insertions(+), 34 deletions(-) copy include/ChangeLog.jit => gcc/rust/ChangeLog (50%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (7e4aa710435 -> 325529e21e8)

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 7e4aa710435 Add ChangeLog directories for modula2 into git_commit.py. new 325529e21e8 Prepare 'contrib/gcc-changelog/git_commit.py' for GCC/Rust 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: contrib/gcc-changelog/git_commit.py | 2 ++ 1 file changed, 2 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022