This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards cd3a4febd5 257: onsuccess: #63: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 924bd27eec 256: force: #62: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards d4ab1b0447 255: force: #61: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 3b399ba1d5 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b3f3e83461 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 55ced848c6 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 874c925aac 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards cb0c4058d6 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c67325ed9e 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards e9002014f7 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9224c36afa 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 00186cd87e 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards acf4c69eea 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ae56a15bf1 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards c85977ed2b 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 38f99c7fb7 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 51ceaaaa4c 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 0e77e9e692 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards e4e38045a9 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ee74426886 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 1cde2cbb80 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards 58a8f8a206 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards bb313d4e26 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards 86ac501b7f 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards ac4405beae 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards 362ee1c784 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 834c8fb358 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards c0b0a98a65 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 778d19605e 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards f275957e4b 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 861a014190 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards aee10d9cac 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 716772cabb 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 16270c57ce 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards d2c8b5fc71 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 1571478897 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 1a0007c578 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] discards 465582386d 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 4b6180a398 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 811df5d82b 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards fd70c3d2ca 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 74a3e4c6d0 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 4d66debb08 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards b8f094f1ed 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards e12f22da88 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 63d06f2830 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9ee03e349f 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 8038d1137f 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards dce68a944f 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 6a25439d58 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 2a2261ebd7 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] discards eaeff9d4a7 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 4e6aea7a20 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 1a4d724c15 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 559c947de3 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards d7f0a22245 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 4099700ec5 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 2c5d319430 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards c0d763945a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards 3cb2aa4da7 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards d1e669234d 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards c5c7431395 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 99dac1a671 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards c739563a50 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 0493ffa79a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards d1416bdbb3 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 0012040f4d 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards 1260ffe703 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards 823e6d2e03 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 3485c3cf30 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards f8a9ae4c0c 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards b28da36530 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards 3d799f18db 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards 0fdf57e0a9 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards 80cf0d6212 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards eeaac198a1 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards 11206fce48 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards 5dc4d6c6e8 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards a8a6b087db 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards 2007c4fa07 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards ad5f8a3865 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards f5aef5c848 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards 5be8598f5e 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 6bc3077c89 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 36f67f66d6 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards c6cc1b3f93 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards b611e818c6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 3e94897128 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards 710ac02688 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 5463b2cb6e 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 0c112f909c 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards 8a58e1ffe1 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 90b8c38904 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards e65ba89da7 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 93b6ecd6f4 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards 376b34e4eb 162: onsuccess: #624: 1: Success after linux: 10 commits discards 366f7d1903 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 6b0f683982 160: onsuccess: #621: 1: Success after gcc: 11 commits discards e09bfb5bff 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 5f58849101 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards ee568258f5 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new 702edb7bd9 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new bbd9f285d5 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new a3611d14db 159: onsuccess: #620: 1: Success after binutils: 12 commits new 522397e3dd 160: onsuccess: #621: 1: Success after gcc: 11 commits new d796bf95c2 161: onsuccess: #623: 1: Success after glibc: 9 commits new 051812ff91 162: onsuccess: #624: 1: Success after linux: 10 commits new 27a14d8bf6 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new 3bd15b39dd 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 6061c5e8a8 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 4b436be89d 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 21112501dd 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new 677d8b93cb 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new f12523b0ba 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new d612dd004a 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new a7f17a156a 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new c36224c437 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new fab8292e4d 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new cf5a6f0c05 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new e075ad7c7e 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new bc347ccc46 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new acb4d8b696 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 114c0e5469 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new c30d5cacf2 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new 3143087157 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new db116e543c 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new aaef2e6b2c 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new e7d8a99a7d 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 75291274ea 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new 5081b5596e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new ab1838a736 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new d6cec86655 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 3006219c8f 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new bc6290861a 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 007c21e309 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new 9bd8fb6ac5 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new b3430bf9f8 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new cd385686be 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new a9fbc94183 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 31ca91e286 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new c982f21cb6 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 236463055a 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new 5d49b1cf77 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 56ac379a21 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new 46c40eb619 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new 58e733a1a3 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new ef94b93439 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new f889f3641f 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new d5d5388ec4 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new bd87ccd6fe 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new d7bfd7c47f 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 7db636268b 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] new 3388afcb5d 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new f05cf26ea1 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 1e97f22930 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new d7bfc23228 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 47f0038f5f 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b092fa4b31 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new b3caf85268 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 12545c24f0 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new f4be11a911 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 32db04db6c 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new e0463c31b5 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 5ed2b2bc7b 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 1ad28edfa5 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new ed7f55f65c 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new d0ae86c70f 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 6497efa234 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new e64c8686d2 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 29db781a5e 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 7bffa86eef 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 6e19edd228 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 51cf9f034d 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 6de93d7fc9 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 3454c3a380 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 82c4433ced 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 6c7135e8b8 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 817ac807b6 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new aa806f0aa0 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new 057c80e3bd 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new b48d3e9dd7 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new 378e1ca0eb 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new fdd18f25fb 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 1129007886 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new a968fe8ed3 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new d7c520679d 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 765c398d65 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new f198a4744f 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 5838669082 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 9a012035ea 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7b55095ebf 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2e7e40b4a5 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6dce1ef6a3 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b022417156 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3479ce1d1a 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b057e164a8 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 48d2af9155 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8b64fc3e7c 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c58efbf0be 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ca71fae26d 255: force: #61: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 0763c6ae41 256: force: #62: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 58810dcfa4 257: onsuccess: #63: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2a2d7476da 258: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...]

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 (cd3a4febd5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/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: 00-sumfiles/g++.log.xz | Bin 2887568 -> 2872328 bytes 00-sumfiles/gcc.log.xz | Bin 2517984 -> 2458196 bytes 00-sumfiles/gfortran.log.xz | Bin 956624 -> 962244 bytes 00-sumfiles/libatomic.log.xz | Bin 2280 -> 2284 bytes 00-sumfiles/libgomp.log.xz | Bin 234296 -> 234132 bytes 00-sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes 00-sumfiles/libstdc++.log.xz | Bin 479756 -> 464328 bytes 01-reset_artifacts/console.log.xz | Bin 2180 -> 2216 bytes 02-prepare_abe/console.log.xz | Bin 2452 -> 2476 bytes 03-build_abe-binutils/console.log.xz | Bin 49344 -> 50432 bytes 04-build_abe-gcc/console.log.xz | Bin 235480 -> 239420 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 9196 bytes 07-build_abe-glibc/console.log.xz | Bin 233636 -> 234128 bytes 08-build_abe-gdb/console.log.xz | Bin 46748 -> 46980 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3864 bytes 10-build_abe-check_gcc/console.log.xz | Bin 8016 -> 7820 bytes 10-build_abe-check_gcc/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1664 -> 1552 bytes 11-check_regression/results.compare | 18 ++++----- 11-check_regression/results.compare2 | 73 ++++++++++++++++++---------------- 12-update_baseline/console.log | 70 ++++++++++++++++---------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 18 ++++----- manifest.sh | 28 +++++++------ sumfiles/g++.sum | 36 +++++++++++++++-- sumfiles/gcc.sum | 2 +- sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.sum | 2 +- sumfiles/libitm.sum | 2 +- 35 files changed, 152 insertions(+), 113 deletions(-)