Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (b89e2f5489 -> 5bb155e2d8)

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 b89e2f5489 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 4bed055a0e 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards c41828dda0 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 3e559104de 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards e062a7c504 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards da7007cf6f 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards a52142e461 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 120aac8b69 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 18435bbcaf 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 667b1327d0 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 28a999db0d 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards b15472d3ea 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 718e54093a 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards bb765a31cf 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 576309a28b 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 34e2724226 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards ce05eea523 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 0fa0acda07 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards ceae32393f 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards c2938fb587 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards bf23c6b056 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 8745db8932 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 9dcdfa372c 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 6584cce26c 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 240e7c8f9d 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 32d24791ef 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 384d585977 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards e0456c1186 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 3a1bd2779b 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 040cab1f72 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards c7baaaa773 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 64b79f0523 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 8757ea7836 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 9dad8dc1b2 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 8e2b6ef214 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 12ec18350b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 1fdcb11f68 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 2f1d83fe46 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 10d94784d7 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 3b974e75d9 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 501a144c35 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 0593a9d350 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 717e51540d 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 7135a621ba 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 94169f574c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 001740ef8d 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards fc8aed4707 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 52472bcd21 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards ccd21b3684 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards dc7271f0d2 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 6fcc4799fa 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 8cb46c1b40 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 47ca2f1f47 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 4883529226 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 5994fbbc6d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards ac358ececc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 313bf8185c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards befee5517e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 52b451661e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards fb40f3dc52 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 3ca72c905c 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 7b67efb002 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 3694c08654 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 73ad2fdc6a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards a6e52e8684 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 1f0cbf055b 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 1a3256bc17 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 3aa94bfa92 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards af2e25c483 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 7766c86507 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards ee3357626c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards a0084807b1 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 7a1f58d85d 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards d26e05613a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards fb37be2af8 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 1b4acff807 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 031a761183 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards c1277208ad 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards f86b39a727 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 3999f65c65 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards a39c3a62d5 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 0fa2f3ef24 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards a727d8b21a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards ba8656b62e 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 0d1bfc7274 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards c4000d8744 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards b08bf6fc99 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 8b58724150 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards a9a71862c2 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 96a1d360b1 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards c7c6690422 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards a8a1878130 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards a4087f5508 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards fef598a657 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 94e618ed7d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 8127ad2c35 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 4fe619ff78 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 5acb9474b3 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4876837d26 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 7b77fdedeb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 01620b5dca 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 531248f42a 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new ece4ba4197 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 7c1a695e58 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 3d62f68ca1 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 83a03931af 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 9672047edb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 9648d2c5e2 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 8589058288 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 2f3dd29dc3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 45bffc4a5d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 8044cd8e80 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 81d186c3ac 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new f7e6069614 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 3be7ca46ca 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new bfb44cbae7 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 575bc428ba 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 76d4438193 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 9dcbeb2118 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 4611ca772d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 1e272a83d0 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new de9fc73aff 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 9614802aa6 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 9f00532b15 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8e692c7731 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 32d9c9866a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 20321103ee 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 484d42ef4e 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 6f8283770f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 44d69530c5 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 1a385f1bc2 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 931509fd40 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 88e6f24546 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 039e002721 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 8103074ba8 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new b036848620 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 569dd57f27 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 8b2ce4a05f 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 395c5228c1 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new a4f7894afe 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 3371de5e73 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 5a5cb7537e 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e379d3c050 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 0b15a42867 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 2c7cacdc54 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new ecb8a20ed8 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 66b7f62a97 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new acdd6c9e8f 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 2d29971cde 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new c2ad13c245 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new f064fad4bc 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new f4f1186f85 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 51c5faca3d 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 9bc7408b91 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new eeb9759481 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new e987ce5802 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 901daa5923 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 0eab79880a 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 7180aeae1a 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 654239215f 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new ce829f3f61 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 8167dc3660 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 08349e8693 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new df87804293 411: onsuccess: #2232: 1: Success after gcc: 3 commits new f76a99211c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new c640cb8ef6 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 77a6b727cf 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 5c885d3007 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new de3230cb07 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 194181d433 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 1f518ecfcf 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 161d216bf9 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 595ca256bd 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new e5e243c5de 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new d78f7ed27c 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new ce07ab7650 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 2d900e281d 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 0acc0e1bab 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 43888f6720 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new bd505f2934 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new e4c5567a0e 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new aec4c304cd 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 620a26c9bb 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new b5bf7ff5bd 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 2c1551918d 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new cb4073ad33 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 79f1f11f18 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new b87cef4391 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new c7ffc87c03 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 5f4ac7804b 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 8843fd0b82 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 7db06e4b55 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 40c37bf072 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 0e0d518575 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 474747a6eb 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 8a966efaa4 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new b10d6c114b 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new c45c1ee238 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 38491c1645 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 07168f1514 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 3ea1768825 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 7b39338dbd 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 5bb155e2d8 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] 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 (b89e2f5489) \ 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 1804 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30960 -> 30804 bytes 04-build_abe-stage1/console.log.xz | Bin 89312 -> 89584 bytes 06-build_abe-linux/console.log.xz | Bin 8808 -> 9472 bytes 07-build_abe-glibc/console.log.xz | Bin 235452 -> 235840 bytes 08-build_abe-stage2/console.log.xz | Bin 225296 -> 225940 bytes 09-build_abe-gdb/console.log.xz | Bin 39176 -> 38980 bytes 10-build_abe-qemu/console.log.xz | Bin 32148 -> 32416 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3808 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2936 -> 3064 bytes 13-check_regression/console.log.xz | Bin 28624 -> 8312 bytes 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 6020 ++------------------------------- 14-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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- sumfiles/g++.log.xz | Bin 2649328 -> 2662032 bytes sumfiles/g++.sum | 89 +- sumfiles/gcc.log.xz | Bin 2225412 -> 2204096 bytes sumfiles/gcc.sum | 124 +- sumfiles/gfortran.log.xz | Bin 895052 -> 900492 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216808 -> 216808 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439516 -> 426508 bytes sumfiles/libstdc++.sum | 19 +- 40 files changed, 549 insertions(+), 5849 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (5361b3d2d2 -> 815bf25484)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 5361b3d2d2 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards f92ed4f1b7 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 2e3824d4c5 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards caffdf48b5 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 65bfb62df8 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ba63f2f2b0 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards b2bd755b8b 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards eed49e5ad3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards c49d5ef9bc 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 6542612787 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards a80735d796 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 6c7b428d94 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 349c9e70ee 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 3d0512e9ea 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 7eb0998657 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 01368b1ae4 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards eb826f31be 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 0f9ccf5f07 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 11a86771ac 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 8286306cb3 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards cd290c14a1 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 71cef8e5e4 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 8c84431f2a 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 51fe400515 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 43bd58911a 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 0ef59d786b 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards a0335aeff3 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 4f97110f12 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 9a69347d03 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 6ca7beff81 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 863138d7ae 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards dd234a8d63 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards b688c0ef54 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 22a975894b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 612f1419c2 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 05045ba235 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 692cb32a7d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 100d97848f 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 9bcc62df65 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards 0b0a367e15 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards f1ff0a9c81 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 086c01c89b 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 582aa10fc4 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 2bfaa8b8bb 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards f6cd96b4e2 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 43f2ebaffa 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 3e7e438d4a 149: onsuccess: #684: 1: Success after linux: 10 commits discards 1b6451a06e 148: onsuccess: #683: 1: Success after glibc: 9 commits discards fe8252fa91 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 5a3bd2d55b 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 7faac82223 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards ed093ad218 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 9544a51d3d 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 4e9b5029e5 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 87a7a995c0 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 062346ca90 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards bab4e79da6 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards c5bcf7f4b1 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 694629221d 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards ebbec60188 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards f5a46749ed 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 35ff29a3f0 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards b2cad375ea 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 672f481fee 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 257c44c31f 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 183f78a13a 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 9df180e2b9 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards a843fd0514 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 9dac285745 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 58f64c4997 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 860cab87d7 125: onsuccess: #658: 1: Success after linux: 3224 commits discards b8bf7d5694 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 091c4e4d89 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 1cc2e4a1a4 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards c436f3a45b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards af53099acf 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards ce60d47e83 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 1796a88a29 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 46d303f962 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards dfa78ca86e 116: onsuccess: #647: 1: Success after linux: 3 commits discards dd67f40686 115: onsuccess: #645: 1: Success after binutils: 27 commits discards af4fad68d1 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 3f7b5d84ad 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards e33ff5f356 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 83374a8417 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 38fcb0d840 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 2375af2838 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards a04c6f84ca 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards f3828fd413 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards af659783af 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards b1cc005b26 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 3882e92ae4 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 6e77705bc1 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 436baf8feb 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards e542bb279f 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 7041eaed3c 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 4822dcb74f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards ac43495f46 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 31aa31a9c1 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 52117c0054 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 229765c854 95: onsuccess: #619: 1: Success after binutils: 5 commits new cbe7065606 95: onsuccess: #619: 1: Success after binutils: 5 commits new 517ea52399 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 2d510a001f 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new d2e1a7c363 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 9e875db5e4 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new cd1df41684 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 5a5a510103 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new cb71bd60f9 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new f3ac6dc8c0 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 4934b955b3 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 6e8cf34a98 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 78926cb3fc 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 32248972ba 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new ef6bbc797c 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 4533e05544 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new b63ccc805d 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 73f21b5fab 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new fb6e1ddaeb 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 42f1838718 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 4f9cd9f686 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new a2c157426e 115: onsuccess: #645: 1: Success after binutils: 27 commits new 0eaec857dc 116: onsuccess: #647: 1: Success after linux: 3 commits new 66dddc6df3 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 53fa403851 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new e374d09b1d 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 2f8926ea99 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 60e7da04d6 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 52a47e7caa 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 6e57286c56 123: onsuccess: #655: 1: Success after binutils: 22 commits new 9567a3dcb1 124: onsuccess: #657: 1: Success after glibc: 2 commits new 992ed247cd 125: onsuccess: #658: 1: Success after linux: 3224 commits new 6fa7583942 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new b051211bd0 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 56ab042792 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 47361ded89 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 00cfe66954 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new c70307dae8 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new cbd7d4bee0 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 13ead4efd6 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new aa3cb71d40 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 110b5c5f6d 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 3525d44c52 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 077f51799e 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 0c380cb421 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new d52682d6b3 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 31f659f36b 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 58f6f7ee36 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 8512c9cfb7 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 2fe6b86343 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 0239f4327e 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 1310f28c27 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 7f419a603b 146: onsuccess: #680: 1: Success after binutils: 20 commits new 066987bef4 147: onsuccess: #681: 1: Success after gcc: 6 commits new 0833387822 148: onsuccess: #683: 1: Success after glibc: 9 commits new 012a867eb5 149: onsuccess: #684: 1: Success after linux: 10 commits new dd1629a652 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new ee9d191db9 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new a9df4ad999 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new f4c2ae58c8 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 6c4f8cda75 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 018726b6e9 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 5e7bcafff5 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 1dfda751cb 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new aaf2fa465a 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 802384263b 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 18430ef8c2 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 2a328db758 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new e4e119f5a2 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 2d7497e878 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 1aeeda14be 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new f5d75c3054 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 66897a03b1 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 7e75577d85 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 2cdb89d38b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new fc43f03c34 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new ac50f83e65 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 6563c222b1 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 5198defe1b 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 3eebd4a090 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 113c093b91 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new b0050594f8 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 5b570a0714 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 83516c4f1f 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new edc4b9a57f 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 4e3509157c 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 64dc73eb44 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 03c27554aa 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 17d5187f62 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 78a832863a 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 02d7a2e67e 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 995c12160b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 9681ac6488 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new a7ecde1297 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 674defd4d0 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 709089f614 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 211366f152 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new da83f32d6e 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 832ba9357b 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 9cf339d302 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new a70908559f 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new bf3530c60c 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 815bf25484 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] 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 (5361b3d2d2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1740 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 38916 -> 38632 bytes 04-build_abe-gcc/console.log.xz | Bin 203056 -> 203924 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8776 -> 9404 bytes 07-build_abe-glibc/console.log.xz | Bin 243572 -> 244160 bytes 08-build_abe-gdb/console.log.xz | Bin 39020 -> 39016 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3792 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2284 -> 2184 bytes 11-check_regression/console.log.xz | Bin 6280 -> 6236 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 21 +- 12-update_baseline/console.log | 38 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- sumfiles/binutils.log.xz | Bin 63016 -> 63104 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83900 -> 83984 bytes sumfiles/gas.sum | 278 +++++++++++------------ sumfiles/ld.log.xz | Bin 122308 -> 122332 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 409 insertions(+), 398 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (392f399ae05 -> e3837b6f6c2)

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 392f399ae05 rs6000: Allow powerpc64 to be unset for implicit 64 bit [PR108240] new e3837b6f6c2 tree-optimization/108950 - widen-sum reduction ICE The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.dg/vect/pr108950.c | 13 +++++++++++++ gcc/tree-vect-loop.cc | 17 +++++++++++------ gcc/tree-vect-patterns.cc | 4 +++- 3 files changed, 27 insertions(+), 7 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/vect/pr108950.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-Os updated (702acf2f23 -> 1b35161cab)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-Os in repository toolchain/ci/base-artifacts. from 702acf2f23 70: onsuccess: #6: 1: [TCWG CI] No change after binutils/gcc [...] new 1b35161cab 71: onsuccess: #7: 1: [TCWG CI] No change after binutils/gcc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2128 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31920 -> 31540 bytes 04-build_abe-stage1/console.log.xz | Bin 73268 -> 72320 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8852 -> 8748 bytes 07-build_abe-glibc/console.log.xz | Bin 246340 -> 245628 bytes 08-build_abe-stage2/console.log.xz | Bin 180720 -> 178080 bytes 09-benchmark/benchmark-build.log | 104 +- 09-benchmark/benchmark.log | 102 +- 09-benchmark/console.log.xz | Bin 3948 -> 3956 bytes .../compare-results-vs-first-internal.csv | 211 +- .../compare-results-vs-prev-internal.csv | 225 +- 10-check_regression/console.log.xz | Bin 15024 -> 14760 bytes .../csv-results-vs-first-1/md5sum.csv | 2144 +- .../csv-results-vs-first-1/perf.csv | 2739 +- .../csv-results-vs-first-1/results.csv | 11484 +- .../csv-results-vs-first-1/size.csv | 934773 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 28 +- .../csv-results-vs-first-1/vect.csv | 16 +- .../csv-results-vs-prev-0/md5sum.csv | 1601 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2600 +- .../csv-results-vs-prev-0/results.csv | 10716 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 7599 +- .../csv-results-vs-prev-1/md5sum.csv | 2144 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2739 +- .../csv-results-vs-prev-1/results.csv | 11484 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 934773 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 28 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 16 +- .../output-bmk-results/exe.improvement | 9 - .../output-bmk-results/exe.regression | 10 +- .../output-bmk-results/extra-bisect-params | 2 +- .../output-bmk-results/symbol.improvement | 3 +- .../output-bmk-results/symbol.regression | 12 +- 10-check_regression/results-vs-first-brief.csv | 64 +- 10-check_regression/results-vs-first-full.csv | 2601 +- 10-check_regression/results-vs-first-internal.csv | 225 +- 10-check_regression/results-vs-first.csv | 225 +- 10-check_regression/results-vs-first.log | 1322 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 18 +- 10-check_regression/results-vs-prev-full.csv | 2851 +- 10-check_regression/results-vs-prev-internal.csv | 233 +- 10-check_regression/results-vs-prev.csv | 233 +- 10-check_regression/results-vs-prev.log | 1376 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../410.bwaves/results-metadata.json | 14 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 14 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 14 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 14 +- .../437.leslie3d/results-metadata.json | 14 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../447.dealII/results-metadata.json | 14 +- .../450.soplex/results-metadata.json | 14 +- .../453.povray/results-metadata.json | 14 +- .../454.calculix/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../462.libquantum/results-metadata.json | 14 +- .../464.h264ref/results-metadata.json | 14 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../471.omnetpp/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../482.sphinx3/results-metadata.json | 14 +- .../483.xalancbmk/results-metadata.json | 14 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 42 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 94 files changed, 963625 insertions(+), 971839 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allnoconfig updated (36921cde97 -> 003f4ba23b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 36921cde97 47: onsuccess: #1: boot: Success after binutils/llvm/linux/q [...] new 003f4ba23b 48: onsuccess: #2: boot: Success after binutils/llvm/linux/q [...] 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 1768 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30984 -> 31156 bytes 04-build_kernel_llvm/console.log.xz | Bin 65820 -> 67408 bytes 05-build_abe-qemu/console.log.xz | Bin 32256 -> 32936 bytes 06-build_linux/console.log.xz | Bin 3060 -> 3068 bytes 08-check_regression/console.log.xz | Bin 4352 -> 4436 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 26 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allnoconfig updated (c815a8aa2a -> 2493655ad3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from c815a8aa2a 44: onsuccess: #1: all: Success after binutils/gcc/linux/qem [...] new 2493655ad3 45: onsuccess: #2: all: Success after binutils/gcc/linux/qem [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30692 -> 30920 bytes 04-build_abe-stage1/console.log.xz | Bin 89248 -> 89504 bytes 05-build_abe-qemu/console.log.xz | Bin 32076 -> 32428 bytes 06-build_linux/console.log.xz | Bin 4024 -> 4008 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4192 -> 4212 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 24 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-arm-master-O2 updated (7367b2dbb1 -> acd7ec4ab7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-arm-master-O2 in repository toolchain/ci/base-artifacts. from 7367b2dbb1 80: onsuccess: #6: 1: [TCWG CI] No change after v6.1.14-4559 [...] new acd7ec4ab7 81: force: #7: 1: [TCWG CI] 437.leslie3d slowed down by 29% [...] 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 2112 -> 2100 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31640 -> 31336 bytes 04-build_abe-stage1/console.log.xz | Bin 91004 -> 90360 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8916 bytes 07-build_abe-glibc/console.log.xz | Bin 237104 -> 237172 bytes 08-build_abe-stage2/console.log.xz | Bin 214616 -> 214124 bytes 09-benchmark/benchmark-build.log | 151 +- 09-benchmark/benchmark.log | 149 +- 09-benchmark/console.log.xz | Bin 4108 -> 4052 bytes 10-check_regression/453.povray.symbols-regression | 1 + .../compare-results-vs-first-internal.csv | 248 +- .../compare-results-vs-prev-internal.csv | 254 +- 10-check_regression/console.log.xz | Bin 14820 -> 15572 bytes .../csv-results-vs-first-1/md5sum.csv | 2866 +- .../csv-results-vs-first-1/perf.csv | 3392 +- .../csv-results-vs-first-1/results.csv | 63264 +- .../csv-results-vs-first-1/size.csv | 712134 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 17242 +- .../csv-results-vs-first-1/vect.csv | 44 +- .../csv-results-vs-prev-0/md5sum.csv | 2504 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3397 +- .../csv-results-vs-prev-0/results.csv | 69487 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 510380 +++++++------ 10-check_regression/csv-results-vs-prev-0/sve.csv | 16360 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 56 +- .../csv-results-vs-prev-1/md5sum.csv | 2866 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3392 +- .../csv-results-vs-prev-1/results.csv | 63264 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 712134 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 17242 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 44 +- 10-check_regression/exe.regression | 1 + 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 18 + 10-check_regression/mail-body.txt | 18 + 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement | 2 - .../output-bmk-results/exe.regression | 1 + .../output-bmk-results/extra-bisect-params | 2 +- .../output-bmk-results/symbol.regression | 6 + 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 3242 +- 10-check_regression/results-vs-first-internal.csv | 252 +- 10-check_regression/results-vs-first.csv | 252 +- 10-check_regression/results-vs-first.log | 1398 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 24 +- 10-check_regression/results-vs-prev-full.csv | 3496 +- 10-check_regression/results-vs-prev-internal.csv | 254 +- 10-check_regression/results-vs-prev.csv | 254 +- 10-check_regression/results-vs-prev.log | 1742 +- 10-check_regression/results.regressions | 20 + 10-check_regression/symbol.regression | 7 + 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../410.bwaves/results-metadata.json | 8 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/416.gamess/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 8 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../437.leslie3d/results-metadata.json | 8 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../447.dealII/results-metadata.json | 8 +- .../450.soplex/results-metadata.json | 8 +- .../453.povray/results-metadata.json | 8 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../462.libquantum/results-metadata.json | 8 +- .../464.h264ref/results-metadata.json | 8 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 8 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 8 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 8 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 128 +- dashboard/squad-vs-first/summary-annotation.txt | 1 + mail/jira-body.txt | 22 +- mail/mail-body.txt | 22 +- mail/mail-subject.txt | 2 +- manifest.sh | 11 +- results | 20 + results_id | 2 +- 108 files changed, 1052228 insertions(+), 1160250 deletions(-) create mode 100644 10-check_regression/453.povray.symbols-regression create mode 100644 10-check_regression/exe.regression create mode 100644 10-check_regression/results.regressions create mode 100644 10-check_regression/symbol.regression -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (c8b745ffb8 -> fb429e3502)

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_gdb/master-arm in repository toolchain/ci/base-artifacts. discards c8b745ffb8 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 13eb376d45 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards d0161a79f8 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards d220c95bc3 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards d0985a595c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards a3b5011673 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards f95c168341 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 34735321ab 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards cc86c265de 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 5af6fe51eb 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 35790a77ac 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 79662b940f 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards c0c10b5b5f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards c77847fb82 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 78970c35ce 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 32f50b4108 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards abc14995ef 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 1b7e179ac8 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards db26e44e71 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 47c862fd0c 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 1428a44e52 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 590869c172 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards a0a2946128 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 854f237041 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 3fc6fb3b4e 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 7aebaba930 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 7d9ec22e45 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 76817de25f 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 959e5cd14a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 5d3594a4e6 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 0997c33d0a 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards fb07a48362 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 33a7c82ce6 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 8ea5819fe5 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards d7534ab416 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 637c38c011 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 0d0c20b6cb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards f35754584d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 8a74673d8d 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 3823e1da59 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 7e3ab8d840 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 0ed6e796ac 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards c4ed9457c8 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 18e2daa39a 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 08c52b14c2 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 56d2893bd5 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards d93c1d60d5 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards e1ac954322 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 4baaa812a2 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 3cdffc39ec 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 0e2634f373 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 01e9b48bc9 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 5880dc8d64 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 78d0ab25e3 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 266c7539f5 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards da0fe5c7cb 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards cf7d7c69fc 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 373e5480a1 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 60d3adcc28 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 334e299e69 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 854211a2eb 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 396c998a6b 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 17e7f614da 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards fa0b31f5f0 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 2fb682c67d 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 1cfc3e2dd9 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 07aaaa81db 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 5c911a18a4 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards e365ee4b37 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 0fc14b6cc3 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 1e4e8b23e1 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards a953291127 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards c658690d5f 125: onsuccess: #614: 1: Success after linux: 12 commits discards 0535dbddb6 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 66377490a6 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards b9c4ae7c49 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards bdcaf38f2f 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards c544542cdc 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 55fb50f6f2 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 3249a89e16 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 39ee598c39 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 6fc1e37fc9 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 88e4155c69 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 589036e3c9 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 724f3a4469 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 28136b6dc3 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards e5c0aa3ee8 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 6e1bde0a3b 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards cc67395cea 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 26caf727a9 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 22482263a3 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 3be4c60f42 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 0fac03f1fc 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 455d00a01d 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 7b513ff42e 103: onsuccess: #589: 1: Success after binutils: 3 commits discards e4a70611e8 102: onsuccess: #586: 1: Success after binutils: 5 commits discards ff9de3836b 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 1d0e23a1f9 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards e271eb5855 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards bd97d4a752 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 6fede3ca98 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 0b2c1cf3d4 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 2e41f0842a 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new b8765bc376 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 32a2475f76 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 0b75e58084 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 95fde8fcef 102: onsuccess: #586: 1: Success after binutils: 5 commits new 1d4d4da47c 103: onsuccess: #589: 1: Success after binutils: 3 commits new 3752b97929 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new edb01a1986 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 93257c9d13 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 03b3c1b598 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 8e2b23216b 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new aae69ccfa2 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new dd17aac32e 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new e8af69a095 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 6bfd80e54b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new b8aa567d7f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 1e00c18c7c 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 829ce15cd3 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 7600ef64a8 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new c3de33d93f 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 0d5454afc7 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new a5633832b6 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new f4fb968e22 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new b4dcb1236b 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new f1346e7602 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 5fa411b600 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new 6a651d454d 124: onsuccess: #612: 1: Success after binutils: 18 commits new 8a4056b466 125: onsuccess: #614: 1: Success after linux: 12 commits new dbcb588382 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 6dbda8fcda 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new b6ea71293f 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 7380b9bbf2 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 1edfe6a97d 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new eace08e5be 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 43a6410d10 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 04742d4e65 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 6a046afcb5 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new ebc7cfdc93 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 2ca9293378 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 6be16df7a2 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 83a0f13982 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new d98516b682 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new a60f51fc83 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 9071ba14ca 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 1fd1e9d7aa 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new cf61638f0e 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 64600aafa4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new ad400dd1c1 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 1057a07b4e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 9788591495 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 4faeada093 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new e29dde6a1c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 03ff4f8971 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new d8f813394b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 226e2c52d8 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new e1cdf18052 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 07fdbc04bb 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new d4c8286ea1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new f100f44850 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 81970ce7fb 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 96d9da9520 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new d57c7204a3 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new b44bc27cad 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 86d34b7134 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 4c0caa3acb 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new f0f62143ed 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 786c7fc209 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 5c55a1da45 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new a136bb4544 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new f27b75da8c 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new fb3da5b477 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 5f00b1429a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 5f5df19b46 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 02c8d3b7b2 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new bcaccdbb50 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 90625af350 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 1f0912ad44 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new f6702802bc 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new a23f60e2bd 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 08db32da6d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 834b0fcc3b 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 6faaeb2d31 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 062185bd8b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 7b4ecee471 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new a16e8f6f50 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 3f69dc3e20 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new 6843eef68d 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new 869dd54a0b 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 92468ac261 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new e5e8a9102a 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 3b98c2c704 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 7e696af911 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 21d1e6470f 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new c8cbc459af 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 806acd157c 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 1dd3913fca 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new bf2cc735bb 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 08c1b73df3 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 9c06eb737e 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new fcb6c5a6c9 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new fb429e3502 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] 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 (c8b745ffb8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1800 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 52088 -> 52884 bytes 04-build_abe-gcc/console.log.xz | Bin 235716 -> 237924 bytes 06-build_abe-linux/console.log.xz | Bin 8792 -> 9392 bytes 07-build_abe-glibc/console.log.xz | Bin 234744 -> 235356 bytes 08-build_abe-gdb/console.log.xz | Bin 51392 -> 51560 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3748 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2252 -> 2144 bytes 11-check_regression/console.log.xz | Bin 19472 -> 16136 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 55 +- 11-check_regression/mail-body.txt | 194 +- 11-check_regression/results.compare | 97 +- 11-check_regression/results.compare2 | 5683 +++++++++++++------------------ 11-check_regression/results.regressions | 94 +- 12-update_baseline/console.log | 60 +- 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 | 196 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 94 +- sumfiles/gdb.log.xz | Bin 2787424 -> 2794008 bytes sumfiles/gdb.sum | 4200 ++++++++++++++++++++++- 30 files changed, 6839 insertions(+), 3890 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (6622f7e8b89 -> 392f399ae05)

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 6622f7e8b89 testsuite: Fix analyzer errors for newlib-fd new 392f399ae05 rs6000: Allow powerpc64 to be unset for implicit 64 bit [PR108240] 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/rs6000/rs6000.cc | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O3_LTO updated (4e1b0da9ea -> 11cd0e34ab)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts. from 4e1b0da9ea 0: init: #2: 1: [TCWG CI] No change after baseline build: no [...] new 11cd0e34ab 1: onsuccess: #3: 1: [TCWG CI] No change after llvm: 121 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2344 -> 1764 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-build_bmk_llvm/console.log.xz | Bin 104572 -> 99756 bytes 03-benchmark/benchmark-build.log | 146 +- 03-benchmark/benchmark.log | 144 +- 03-benchmark/console.log.xz | Bin 3896 -> 3824 bytes .../compare-results-vs-first-internal.csv | 38 +- .../compare-results-vs-prev-internal.csv | 38 +- 04-check_regression/console.log.xz | Bin 5348 -> 6348 bytes .../csv-results-vs-first-1/perf.csv | 91 +- .../csv-results-vs-first-1/results.csv | 211 +- .../csv-results-vs-first-1/size.csv | 90964 +++++++++---------- 04-check_regression/csv-results-vs-first-1/sve.csv | 12 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 91 +- .../csv-results-vs-prev-1/results.csv | 211 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 90964 +++++++++---------- 04-check_regression/csv-results-vs-prev-1/sve.csv | 12 +- 04-check_regression/results-vs-first-brief.csv | 42 +- 04-check_regression/results-vs-first-full.csv | 101 +- 04-check_regression/results-vs-first-internal.csv | 46 +- 04-check_regression/results-vs-first.csv | 46 +- 04-check_regression/results-vs-first.log | 712 +- 04-check_regression/results-vs-prev-brief.csv | 42 +- 04-check_regression/results-vs-prev-full.csv | 101 +- 04-check_regression/results-vs-prev-internal.csv | 46 +- 04-check_regression/results-vs-prev.csv | 46 +- 04-check_regression/results-vs-prev.log | 712 +- 05-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../508.namd_r/results-metadata.json | 10 +- .../510.parest_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 70 +- git/llvm_rev | 2 +- mail/jira-body.txt | 8 +- mail/mail-body.txt | 8 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results_id | 2 +- 55 files changed, 92544 insertions(+), 92564 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023