Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (a4c7fee788 -> 2da2a874d3)

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-arm in repository toolchain/ci/base-artifacts. discards a4c7fee788 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards 844168c63f 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards 460212b7e8 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards c55b665c27 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards a40cd90b8d 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards 5f1d10cb5b 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards a04a2eb674 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 9104699324 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards dac4b6e7fc 104: onsuccess: #530: 1: Success after gcc: 7 commits discards da5bcad3ef 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 396f352a02 102: onsuccess: #527: 1: Success after binutils: 5 commits discards c8d05b7a2e 101: onsuccess: #524: 1: Success after binutils: 2 commits discards b73b5a8f63 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 9d22cba355 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards c2ab5a4c39 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards b79b6b8cc8 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards caa19093bc 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards dbfeaa17e6 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards c132c3df83 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 3d6bd9a79a 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 3a088cfd88 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 678f1940eb 91: onsuccess: #511: 1: Success after linux: 27 commits discards ac827665d2 90: onsuccess: #510: 1: Success after glibc: 5 commits discards def61ddbde 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 55954d5aef 88: onsuccess: #506: 1: Success after linux: 34 commits discards 3b63ea5d1c 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 168af27680 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 780b5981f1 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 93987ca758 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 3af29c3798 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 8e1be7cf66 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards fc12081229 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 3484d4a8ef 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards edcfcebbaa 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 8fef83cbeb 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 548363f83f 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 9da22fda0e 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards cd49c344f6 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards d1b78a3a44 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 2d698835e1 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards f9d939cd34 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards c95e76623e 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards ffd05fbbee 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards fd140bde0f 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 6a6f8a6b8f 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 63eee4501c 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 942a295751 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards c979ed308b 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 29a384ad23 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 311c54b3e1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards ac4a8ffbe3 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 9856f27ca2 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards bce1902b7d 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards fab7bf1cf1 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 9a2a68520f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 86639b721b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards f94b503063 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 7b93f7165b 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards e57ec48991 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards a73645bc9f 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 078a967ced 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 9ec2fb7520 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 50c846d65b 50: onsuccess: #461: 1: Success after binutils: 12 commits discards f2f78bc7c1 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards f53162bcf2 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 3ab94226cb 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards d0061daf2b 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 5655cedc4c 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 4963be2ce7 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 1e7277d65c 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 89217527ce 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards ffea22251c 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards a8f3e6f320 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 080aaed2f4 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 9b49216f1c 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards ab3d93932d 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 2f68099058 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards b574d27ac3 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards d3b4954aa7 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 4c8ef27eef 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards abe9eea959 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards ece6a88d79 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 74aeeab4bd 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards c915eed763 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards e062e491ad 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 035e852633 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 7af7bb623c 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 45b3b26b7f 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards 89cc963ec9 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 060ee68332 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e7978e1f57 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c7961fcc08 21: onsuccess: 1: Successful build after linux: 79 commits discards 0cfe9acd44 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 49ac6b44f7 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ddfe77a0e9 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 41ae884f3d 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e8a800cbb6 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ac2475255 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e83cff9853 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0276cd19da 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3f7b1b358f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 304d31c63c 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a3ed2097a8 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e5715cb871 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c4fba5c321 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d160ed4eed 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bd0521ce6a 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c050777855 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd11b285b4 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a7f6839efa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 232b3f28e0 21: onsuccess: 1: Successful build after linux: 79 commits new 308fb2907b 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 37c14886c4 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new dba748bf0d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 2f6cb335f9 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 0cc8216441 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new db7e8efb9c 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new bcfaa76ced 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new e2c35fc059 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 94e3d41500 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 5e62372465 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new d21675eb2d 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new ddefb3c785 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new c42b92a495 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 51b3f45ca3 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 5ff3dba10e 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 250eb14def 37: onsuccess: #443: 1: Success after binutils: 2 commits new ccb24fe611 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new f723279882 39: onsuccess: #447: 1: Success after binutils: 5 commits new 2fc8712088 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 7229d95f8c 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 6704172777 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new d4af562055 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 2a5c5cb5ac 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 953ef68973 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 014f550953 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new e41e02a4e0 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new d7f384a65f 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 02def14d88 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 1013ed546a 50: onsuccess: #461: 1: Success after binutils: 12 commits new d62a74877f 51: onsuccess: #464: 1: Success after binutils: 6 commits new 72124428ae 52: onsuccess: #467: 1: Success after binutils: 9 commits new dd8708e10c 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 1bd21cca49 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 1dcacc6179 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 05bc661b0b 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new bea153cfb8 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 5cb1a91e1f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new 1073819ed8 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new a89d2669f1 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new c225aca832 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 15c217e3cc 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new abca15e34d 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 966beb909f 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 0654e99cb5 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 704f13f49a 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 0a62762944 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new d116666a72 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 98315f5d8e 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new cf6cab1004 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new fde9aea884 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 0e0a363b0c 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 1845c5cdd1 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new be50382bd0 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 4270b44cd5 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 16e754a6bc 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new a3230942c7 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 80e3dff5ae 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 565f3391e1 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 11725ea71b 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new ac71e306e5 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new bb94677be9 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 56a44ec816 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new ff144f6f4e 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 01f1b12269 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new b1db87504c 86: onsuccess: #503: 1: Success after binutils: 12 commits new e79f0ad660 87: onsuccess: #505: 1: Success after glibc: 7 commits new 23dfe6c939 88: onsuccess: #506: 1: Success after linux: 34 commits new d79cedbb66 89: onsuccess: #508: 1: Success after binutils: 12 commits new 9da125fd54 90: onsuccess: #510: 1: Success after glibc: 5 commits new a2799ec5c6 91: onsuccess: #511: 1: Success after linux: 27 commits new 8ef383990b 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 6cf5d6e636 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 448c6a59bd 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 0db56929c3 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 5a2b213215 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new af58afa303 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 261f823001 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new fbd304f1d3 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 370efb876c 100: onsuccess: #521: 1: Success after binutils: 10 commits new af67ccc406 101: onsuccess: #524: 1: Success after binutils: 2 commits new 5df70f0d3f 102: onsuccess: #527: 1: Success after binutils: 5 commits new 7f6f0fa49f 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 104366af7a 104: onsuccess: #530: 1: Success after gcc: 7 commits new 0fff60485b 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 011bafe4d5 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new 2946e340b2 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 57293da1e3 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new 41344a1884 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 98305c9ef5 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 1abbe412c6 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 241ca87bd7 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new 2da2a874d3 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] 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 (a4c7fee788) \ 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 1700 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52820 -> 53584 bytes 04-build_abe-gcc/console.log.xz | Bin 233836 -> 234572 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8540 -> 9548 bytes 07-build_abe-glibc/console.log.xz | Bin 235052 -> 234808 bytes 08-build_abe-gdb/console.log.xz | Bin 51920 -> 51352 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2612 -> 2628 bytes 11-check_regression/console.log.xz | Bin 5860 -> 5844 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 62912 -> 62680 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98020 -> 98084 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131508 -> 131524 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 404 insertions(+), 404 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch releases/gcc-12 updated (37a7b2e8a73 -> ed8d7ecac11)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 37a7b2e8a73 libstdc++: Remove unnecessary header from <memory> new 3a34f1f56ad Fix wrong array type conversion with different storage orde new b492e3a0d80 Fix thinko in operator_bitwise_xor::op1_range new ed8d7ecac11 Daily bump. The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 9 ++++ gcc/DATESTAMP | 2 +- gcc/range-op.cc | 3 ++ gcc/testsuite/ChangeLog | 9 ++++ gcc/testsuite/gnat.dg/opt100.adb | 13 +++++ gcc/testsuite/gnat.dg/opt100_pkg.adb | 17 +++++++ gcc/testsuite/gnat.dg/opt100_pkg.ads | 23 +++++++++ gcc/testsuite/gnat.dg/sso18.adb | 21 ++++++++ gcc/tree-loop-distribution.cc | 7 ++- libstdc++-v3/ChangeLog | 94 ++++++++++++++++++++++++++++++++++++ 10 files changed, 196 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gnat.dg/opt100.adb create mode 100644 gcc/testsuite/gnat.dg/opt100_pkg.adb create mode 100644 gcc/testsuite/gnat.dg/opt100_pkg.ads create mode 100644 gcc/testsuite/gnat.dg/sso18.adb -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch releases/gcc-11 updated (6635f128ea8 -> 9b66efb0c95)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 6635f128ea8 Daily bump. new 066e5d93a21 Fix wrong array type conversion with different storage orde new 11a1089a070 Fix thinko in operator_bitwise_xor::op1_range new 9b66efb0c95 Daily bump. The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- gcc/range-op.cc | 3 +++ gcc/testsuite/ChangeLog | 9 +++++++++ gcc/testsuite/gnat.dg/opt100.adb | 13 +++++++++++++ gcc/testsuite/gnat.dg/opt100_pkg.adb | 17 +++++++++++++++++ gcc/testsuite/gnat.dg/opt100_pkg.ads | 23 +++++++++++++++++++++++ gcc/testsuite/gnat.dg/sso18.adb | 21 +++++++++++++++++++++ gcc/tree-loop-distribution.c | 7 ++++++- 9 files changed, 102 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gnat.dg/opt100.adb create mode 100644 gcc/testsuite/gnat.dg/opt100_pkg.adb create mode 100644 gcc/testsuite/gnat.dg/opt100_pkg.ads create mode 100644 gcc/testsuite/gnat.dg/sso18.adb -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch releases/gcc-10 updated (187c235b65c -> ac5044574cc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from 187c235b65c Daily bump. new ac5044574cc Daily bump. 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/DATESTAMP | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (a8404c07e7f -> f9e9a15bb22)

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 a8404c07e7f Fix thinko in operator_bitwise_xor::op1_range new a5878983d53 gcc-changelog: temporarily disable check_line_start new 9a1b4f1d3dc Daily bump. new f9e9a15bb22 Revert "gcc-changelog: temporarily disable check_line_start" The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: contrib/ChangeLog | 5 + gcc/ChangeLog | 245 ++++++++++++++++++++++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/ada/ChangeLog | 15 +++ gcc/analyzer/ChangeLog | 88 +++++++++++++++++ gcc/c-family/ChangeLog | 5 + gcc/c/ChangeLog | 6 ++ gcc/lto/ChangeLog | 6 ++ gcc/testsuite/ChangeLog | 55 +++++++++++ libstdc++-v3/ChangeLog | 27 ++++++ 10 files changed, 453 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/llvm/linaro-scripts] branch master updated (7168ddf -> db7d478)

by David Spickett

This is an automated email from the git hooks/post-receive script. "David Spickett pushed a change to branch master in repository toolchain/llvm/linaro-scripts. from 7168ddf llvmbot monitor: Remove SVE silent bots new db7d478 llvmbot monitor: Move armv7 lnt bot to silent 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: monitor/linaro.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/jenkins-scripts] branch master updated (89b3edb2 -> b26b2b49)

by David Spickett

This is an automated email from the git hooks/post-receive script. "David Spickett pushed a change to branch master in repository toolchain/jenkins-scripts. from 89b3edb2 tcwg-update-llvmbot-containers: Remove SVE silent bots new b26b2b49 tcwg-update-llvmbot-containers: Move armv7 lnt bot to silent 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: tcwg-update-llvmbot-containers.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (2b3a3d7fe34 -> a8404c07e7f)

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 2b3a3d7fe34 lto: fix usage of timer in materialize_cgraph new a8404c07e7f Fix thinko in operator_bitwise_xor::op1_range 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/range-op.cc | 3 +++ gcc/testsuite/gnat.dg/opt100.adb | 13 +++++++++++++ gcc/testsuite/gnat.dg/opt100_pkg.adb | 17 +++++++++++++++++ gcc/testsuite/gnat.dg/opt100_pkg.ads | 23 +++++++++++++++++++++++ 4 files changed, 56 insertions(+) create mode 100644 gcc/testsuite/gnat.dg/opt100.adb create mode 100644 gcc/testsuite/gnat.dg/opt100_pkg.adb create mode 100644 gcc/testsuite/gnat.dg/opt100_pkg.ads -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (bcc2449384f -> 2b3a3d7fe34)

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 bcc2449384f tree-optimization/107865 - ICE with outlining of loops new 2b3a3d7fe34 lto: fix usage of timer in materialize_cgraph 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/lto/lto.cc | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allnoconfig updated (472d57cade -> 4d168b478f)

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-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 472d57cade 23: onsuccess: #473: boot: Success after binutils/gcc/qemu: [...] new 4d168b478f 24: onsuccess: #474: boot: Success after binutils/gcc/qemu: [...] 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 1692 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 31716 -> 32020 bytes 04-build_abe-stage1/console.log.xz | Bin 72984 -> 73096 bytes 05-build_abe-qemu/console.log.xz | Bin 31660 -> 32100 bytes 06-build_linux/console.log.xz | Bin 4632 -> 5132 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3920 -> 3916 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022