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 dfb5f04d04 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards c9103a168a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 0a911938c1 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 3103114af7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 7a4d5c0378 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 501024e375 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards f9cce6a245 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 8fb6aeddfc 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 460a2219e3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 58c8deaf96 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards eb72a4e16a 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards cfd3fcb872 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 646362a365 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 588dda64f7 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards b7fa7b4535 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards e4973e2762 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 74d9153268 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 62f8561227 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards beec01c689 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 838df7ca20 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 8ded91b54a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 6ca4070cee 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 30cf6bd9a6 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards ef3e1a8107 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 7b478954da 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 0f2e9ecf96 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards f9f9f79444 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 823166ae9b 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 492901f7ba 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 7cbeaa4738 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 30239d9a7c 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 447070ca9e 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 621d2e3f32 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards b15a72f559 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 02a5106d5c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 116fdc3d9a 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 17ee70cecb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 3870753d2c 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 294424807a 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 71238dc799 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 5c913f70ad 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 6358bf58f9 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards abc69c328c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 5c9fbbf79c 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 0d55dd7e49 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards c7da0b74bf 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards af24f7ad0c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards a3116252ee 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards c3430228b0 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards add3c7792c 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards a2d3a2d90c 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 45e4832e69 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 5a4d687d24 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards e26ae5a043 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 88abd83237 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards af6d1f2b85 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards b7cd831d26 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards c63c4eb902 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 566f6b3cab 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards bc98f935f3 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards de7c423927 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards cbc1e135c7 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards e3b89c93cc 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards dbda5fe72f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 43a14d600e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 83bde9a47c 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 8f89a575b8 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards c2c3c08a75 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards b665038891 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 535d431488 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards c38657f95b 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards d2f86132bb 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards d9e5143a24 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards e1dc8bd7c5 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 4a606d9524 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 351d13507d 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 92426a3f1e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 83fe58b36e 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards d98487e7d2 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards d74f6ea96b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 2bbad0d8a9 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards d55b7e0bf8 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards ee656daee6 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 5969ee956d 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 58f944af90 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards b97d611465 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 6648db39ed 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 6df66727f2 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards aab9e16d6b 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards a5cc4e4908 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards f4f51d4533 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 27aa9c73d0 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 5494d89690 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards bc102ffe3b 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards e77d2259a8 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards e67baaa4e6 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 3a88df4d2b 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 0c8d3d6859 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 14dbb5bcbd 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 10f424efcc 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 34ba38bf00 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new fa361e3ec3 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 3ec79e5d52 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 2ab8cf471c 235: onsuccess: #2483: 1: Success after linux: 108 commits new 007ae9dac8 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 775f3fc246 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 77b77cae32 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new a1ab5c0e11 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new b4ebf905d7 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new a1235dbe03 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 85988a93cf 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 1c293e6fd2 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 8682e93d11 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new f199257bcb 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 780644081b 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new ec5e2a5021 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new f21ac6bda4 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 98b302510a 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 6f180dd6e0 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new a23935c6b6 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 191cad374f 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 01f01e65ae 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new ef120c904a 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 125bd104dd 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new bc5c8b4de8 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 7a46624e09 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new a5f37b8389 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new e5c7d5ee61 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new e3c5f8a563 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 5f3f15794c 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 56f7c0bc03 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new da29bb6a87 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 1708146dfd 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 694e2fb0aa 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 68122f1c9a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new d823965d88 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new d5a09d9e01 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new e7cf46ca55 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 49c2f87f25 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 950aef12f2 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 46f115f92b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new f3ec40af19 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 24799fa338 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 7a37f808a2 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 456e252e13 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new ade07522b9 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 31eb0d09e5 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 87887cbb91 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 09290f71f9 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new dba22d2d77 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new e7d0ab03e5 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 8cda172fcc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 561e199851 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new e77322a5c3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 8ab902a6f7 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new a1d78e2b39 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 1bcaa99f09 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 3e95859e21 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7f49ec4d4e 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 1e864649b7 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 7a0e71d715 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 75a22d01bc 293: onsuccess: #2542: 1: Success after gcc: 5 commits new ea96beb269 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 0c2bb2f0f8 295: onsuccess: #2545: 1: Success after linux: 10 commits new abd5bfbbf1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 3f6bc4fa23 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 72770b5ae4 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 65b1f462b5 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 6e4762c9ba 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 24f1aa4f64 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new fc0a4090b7 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new df87b83706 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 362b3138ff 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new d36199acf3 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 61b74cc626 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 668812d83a 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 3eca9a0e79 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 15e43914d1 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 041b62f78d 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new eb97bf4f74 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new db8c1afb9e 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 2acaf56276 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 5b5939a606 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new c868121306 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 02f122b857 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 4769cb1b9c 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 9b6357ffe2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 0cd7c22ceb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new f1eb4f49b3 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new b4b74882ed 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 3366e957ff 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new f2ad1184d3 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new afca38bb73 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 6de7419b25 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 522944fab2 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 0db0116bdd 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new c2fa6e7503 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 93da227ede 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new c1c25e93d6 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 2457513420 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 7893cdf4b7 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 864c453eb5 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 71570ba29b 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits

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

* -- * -- B -- O -- O -- O (dfb5f04d04) \ 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 1800 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31988 -> 31752 bytes 04-build_abe-stage1/console.log.xz | Bin 73720 -> 73200 bytes 06-build_abe-linux/console.log.xz | Bin 8784 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 246120 -> 245120 bytes 08-build_abe-stage2/console.log.xz | Bin 206220 -> 204328 bytes 09-build_abe-gdb/console.log.xz | Bin 39652 -> 39120 bytes 10-build_abe-qemu/console.log.xz | Bin 33156 -> 32380 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3960 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3132 -> 2780 bytes 13-check_regression/console.log.xz | Bin 7968 -> 6904 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 33 +- 13-check_regression/mail-body.txt | 132 +- 13-check_regression/results.compare | 73 +- 13-check_regression/results.compare2 | 212 +- 13-check_regression/results.regressions | 73 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 134 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 73 +- sumfiles/g++.log.xz | Bin 3439276 -> 3408304 bytes sumfiles/g++.sum | 47 +- sumfiles/gcc.log.xz | Bin 3032072 -> 3043468 bytes sumfiles/gcc.sum | 4394 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1044160 -> 1037268 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214632 -> 214852 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431616 -> 430296 bytes sumfiles/libstdc++.sum | 7 +- 41 files changed, 2683 insertions(+), 2620 deletions(-)