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-aarch64 in repository toolchain/ci/base-artifacts.

discards 6be0403987 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards b5d6bb9cbc 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 798b390e19 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards c5df7c7fd8 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 689b76989a 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 929073a380 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards e981e0cca8 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 850498fcb2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards c126bb02d8 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 8ccb5bdc2e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 01286364c6 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 73837af59c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards fc7f1bd159 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 87b42e9096 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards fb4228cb35 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 003c1a9e3d 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards a787837f0a 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards f0aaa2e400 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards a5e3c0a886 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 6d3f8c23e4 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 3a1e940800 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 3586ed332b 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 0c6f229dd4 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards b5106e3cfe 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 20219e0fdd 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 99df7d3aee 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 04436227bc 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 8f4a638289 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 7279a0e4a3 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards a8e6abdf99 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 219911f0c6 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 04154a6cb1 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards f31ba3d621 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards bbdc0aee8d 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 4ecc392092 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards ffd30b9322 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 6edc78106a 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 195a9e0595 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards f251f9e803 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b32c4ff589 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards e4e2d08792 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 8191e42cdf 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards fc71727b2b 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 509452f2d1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards ddf0bddae4 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 83f03f78f8 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 9d07ee3dd8 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 1d617ca27e 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 10ce9a1fdc 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 6736449a84 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 679f66f267 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 370f147f51 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 7e01c4857c 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards a6afddb5d0 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 696ae1625f 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards eaa62c597f 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 56a5c7a33d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards b6c69251c8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 2721af6481 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards e39ef79704 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 20a9824c31 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 0fbbe0f52c 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 90a623daea 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 400a1a45fd 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 9f3af1a8fe 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards f24a04b750 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards a4e7553823 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 7a11a57d74 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 5078c43869 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards f627af0369 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 10596bd5e5 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards ba00adedb2 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 338830b6ff 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 258068ea11 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 3368c8f8f5 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards d604b0e6ed 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards c89d7b6c80 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards ad38cbdca4 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards b7a7291a8d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards cb5d631130 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 3d3b7e5b51 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 3adb70d9e8 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards a939bf950e 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 71cdbba841 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 8b48a09ab0 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards baa9cf9eec 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards fdd008993c 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 3232bc399b 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 04b453bcc6 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards f64fee3a6a 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 4a1f9cd925 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards bda90068f2 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 45a7ab8bc0 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 089a6691a0 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards c9c4fa2e79 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards db82f61e5d 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 80c1a224a0 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 7424b6733c 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards cb4bcc5335 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 589a4834f5 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 7e1a94d306 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 67e5494e29 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 57c46221be 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new b525d13e4c 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 75966dea33 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 4987546cf3 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 739df49e5f 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new dfb380f61f 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new fbd9d43c41 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new d7227a1403 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 7d320a7993 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new a2c168f55c 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 37c761f506 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new bbac8ec9a3 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new fc5bd98390 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new d92fcd1329 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new af269947a6 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 539b11fb37 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 79ed08b1c6 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 07499f5317 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new ab7d077d92 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 7ddf2c8003 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 31bc5bb1df 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 92ad99c916 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 25a633a23b 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 88a9fd5465 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 45af95257a 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 40da416796 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 28dcda4861 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new b826fd7604 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 4c576b3188 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 9a89f1bba2 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 96c3f8df31 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 7777ce94af 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a356b20f68 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new f5ffde96cb 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 7f63584571 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 2376b1c8ec 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 77c82bec8e 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new d8bcfa9ca6 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new adf2dafe9b 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new ad03dcccb8 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new a4a1a503f5 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 2674ff6b1b 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 941ca1b533 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new d4481680a2 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new dd76ce61bb 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new f025c0878d 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 4668e47e8c 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 10e62d8ba5 293: onsuccess: #2542: 1: Success after gcc: 5 commits new fea502456d 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new ce756596b9 295: onsuccess: #2545: 1: Success after linux: 10 commits new b974640117 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new de0799caec 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 63d67a78cf 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new ebc1f9799c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new f613550606 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 3e112a96b5 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 0dc1fa0442 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new ca65950e82 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 1f07e49e63 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new e3be94761b 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new b310ad1f8a 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 9faaf58051 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 2122501d30 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 8a1016db93 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new f22866278e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 3e11aef27e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new ee1b691216 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 68758eae31 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 4ab6269684 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 1533448527 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new d0d482d775 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 044ae8dc4f 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 56507d3bc2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new d4e3030bbd 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 41ede7055d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new abfe22988c 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 7c21b54a26 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new f6b1556d31 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 48fdbba151 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new e7b7c9d97b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new c36b3cfb74 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 2197085ea6 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 1d21aaa10d 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new b770f0574c 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 613915c04b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new f81a8bce07 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 6b892725cb 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 9c96479a2d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new da9a8baee2 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new fc99e09878 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new d1831cb268 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new d7f19d8705 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 0fd219241d 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new bf1610e779 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new b6ed6f8247 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new e0f4a899f9 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 027f65cf98 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 5d4d4952d3 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new c31d1277ef 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 2b63661e72 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 15632191fd 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (6be0403987) \ 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 1812 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31276 -> 31892 bytes 04-build_abe-stage1/console.log.xz | Bin 73496 -> 73948 bytes 06-build_abe-linux/console.log.xz | Bin 9232 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 244360 -> 246216 bytes 08-build_abe-stage2/console.log.xz | Bin 204712 -> 206972 bytes 09-build_abe-gdb/console.log.xz | Bin 38484 -> 38928 bytes 10-build_abe-qemu/console.log.xz | Bin 32012 -> 32272 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2924 -> 2524 bytes 13-check_regression/console.log.xz | Bin 7692 -> 6996 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 19 +- 13-check_regression/mail-body.txt | 138 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 102 +- 13-check_regression/results.regressions | 41 +- 14-update_baseline/console.log | 70 +- 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 | 140 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 41 +- sumfiles/g++.log.xz | Bin 3401972 -> 3427448 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3022940 -> 3014460 bytes sumfiles/gcc.sum | 3772 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1036420 -> 1034576 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215120 -> 214812 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2660 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429012 -> 427264 bytes sumfiles/libstdc++.sum | 36 +- 43 files changed, 2183 insertions(+), 2317 deletions(-)