Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[gcc] branch master updated (1bdba731b9c -> 7e4aa710435)

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 1bdba731b9c libbacktrace: rewrite and simplify main zstd loop new 7e4aa710435 Add ChangeLog directories for modula2 into git_commit.py. 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: contrib/gcc-changelog/git_commit.py | 2 ++ 1 file changed, 2 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (f4cabb5ef32 -> 8b38bac66f8)

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-aarch64 in repository toolchain/ci/base-artifacts. discards f4cabb5ef32 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] discards a6c3f0c8df6 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] discards 94368c5d0bb 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 2cd80e863df 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards f68ad4971d6 202: onsuccess: #2431: 1: Success after linux: 944 commits discards bed5c68d254 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards ff2976e8cdd 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 8f93f2f0ce5 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] discards de0907beab1 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] discards 6ed5e8bc685 197: onsuccess: #2348: 1: Success after linux: 190 commits discards c4594be69be 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] discards 813533868bd 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] discards 1dfb20f7f31 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] discards 866731c6b31 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] discards 9f6f82e1cc9 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] discards 9f904180e99 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 81cd8932142 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] discards 98ba49e4a0f 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] discards 96df0bac828 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] discards d73e2ba2045 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] discards 4e73a4ff04f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] discards 18dd76ae2ed 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] discards aae59b0df96 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] discards f4e8b66fc58 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] discards 3e688c4fadd 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] discards c48a48879e3 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] discards e94060592bc 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] discards de94796374b 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] discards b7df8acc9e6 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 5acbf14f778 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards a2d2b72bffc 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards b654249a91e 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 9639742d807 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] discards 573cc6c06c4 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards b58dc774f81 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards b53ff1bf3c1 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] discards dee69d8bde8 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] discards d8d9ab3e6fd 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] discards 637a1c823d9 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] discards f7c7e60de97 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] discards 75e0c14e6e1 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards aa89eaa924f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 45f14301215 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] discards 0fd4004fa13 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] discards b6b4e148707 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] discards bf3cf6f45ea 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] discards 71afbc27708 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] discards 222fa0cfad8 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] discards 58656e5c9e8 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 75271f48d14 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] discards 20709c0064b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] discards 01438ce65fa 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards ba2abe2a19d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] discards c3616d6f186 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] discards 3863cee678c 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] discards 89168cc8a60 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 827c7db0432 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards fb8404304a6 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards a61f4e56fcd 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] discards dc1d8556d32 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] discards 0b5b00e1a73 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 93c53fa16aa 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards 915a39511f0 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] discards 44a31c9c0fe 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] discards a2c90cf9114 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 24a7fa23c78 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] discards 60508aa3a11 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] discards 1085db7593a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] discards cafd00070ed 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] discards 9b40b854dac 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] discards 23894730462 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] discards 2dafb2f9c4e 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 7cad0ddfe74 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] discards 76f101f607d 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] discards 9704da47138 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] discards 7fbeca6760d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] discards e6b9661f53e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] discards 1bacd2dff70 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] discards d122e23325b 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 20837dd4ee5 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 3b388511e26 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] discards 32411ef44b2 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] discards 3544b108b1b 124: onsuccess: #2159: 1: Success after linux: 23 commits discards e9b846dce15 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] discards d536ae933c4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] discards c117c7163fa 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] discards 90d516d34e1 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] discards 2082eb8e2fe 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] discards 86d9050a8c2 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] discards 1adbc11ddf0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] discards 5a5e991ed65 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] discards e7e719f5c06 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] discards 16a15887730 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] discards a8ad5401210 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] discards c07d53e1408 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] discards 32bde74b07f 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] discards 2e7b1dbbfcd 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] discards 60ce40b5117 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 3c0c6d0a452 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] discards ebf3f282cef 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] discards e38eefb0eaf 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] new 80dea9cd725 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/ [...] new 88186abe856 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 [...] new b3515c0f41a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 [...] new d11adda3da0 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 962c33071c3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] new 39cde609f6b 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] new ed11b1c1e3f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] new 77d0686260e 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] new 73d6599c662 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] new 96256649e64 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] new d1d292df3a1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] new ce9836d8a62 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new 82260cba6eb 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] new d27632ef603 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] new f7c78f3a679 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] new 14574060ef6 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] new 9998fda13f6 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] new 0d6344ae30f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] new 3fb9a2ef27b 124: onsuccess: #2159: 1: Success after linux: 23 commits new 8eff0fd3e87 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] new e8be657d200 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] new 605d750d8cb 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 5e84f5ea19e 128: onsuccess: #2163: 1: Success after linux: 23 commits new eac485419e1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] new 3f0ad09c720 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] new b0bcdd28e2a 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] new 7c438bf0880 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] new 30861262b5b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] new 83e028e1b73 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] new 926c7e19a04 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 65ee7fe9cf1 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] new aa8914ca0e3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] new af728b6af85 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] new bb5d1bb35ef 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] new c34243399d0 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] new 6bb919ddca7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] new f97b29a9684 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 87d74670117 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] new 9be27d22a1b 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] new b0ab586071b 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new e46ff737a5f 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new aedbabbc503 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] new 36436fac229 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] new 0f0dfe99ece 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new f41216d648b 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 8e88a5caf84 151: onsuccess: #2186: 1: Success after gcc: 2 commits new b473776b868 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] new 222db36dd46 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] new 97f70597703 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] new 4d8f404f31d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 7f60bcf2d92 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] new 825ab2817aa 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] new 2f1b36fcc2c 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new 6e39b8211e1 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] new f65b4f72967 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] new cfe535ab8fb 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] new b34b25cbbe1 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] new 1f265c5ddda 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] new 6cc3fd5a9e1 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] new c3df6202944 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new a7dadf3ee26 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 0433c5d419d 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] new c1bbccf3cfd 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] new aba535d7318 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] new 4d67c5bc565 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] new 36dbd8f0f68 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] new 2f95da19b39 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 95e0df75a96 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 491b9db8621 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] new c654e7fcbc9 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 1dc531f01f9 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new 7b807b39712 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new d3782ddc37e 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new 5da2f8d7fa9 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] new dd9de0d4b1f 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] new 60f300279a8 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] new 46195be54a0 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] new 34d533d6c07 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] new 8f9208de381 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] new 1aef349cffd 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] new 3d8f78eed45 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] new db32aeadd80 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] new 5fe6b0e5ef6 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] new a6d5de999e9 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] new a8adc57f48e 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] new 141c1c1ac31 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 28747dbbb76 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] new 9c99f2709fa 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] new 9b8baf00225 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] new e919f3a5e2b 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] new e1e74d70401 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] new d41432c00c1 197: onsuccess: #2348: 1: Success after linux: 190 commits new 3bff5771918 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] new 21a61c3426f 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] new 8fc700117e0 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 651e7e8cc50 201: onsuccess: #2430: 1: Success after glibc: 26 commits new e615d6ab172 202: onsuccess: #2431: 1: Success after linux: 944 commits new d6f5d2eeb09 203: onsuccess: #2433: 1: Success after binutils: 27 commits new a6bea97e9c0 204: onsuccess: #2435: 1: Success after linux: 3 commits new 6990f812e98 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] new b60cd679846 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] new 8b38bac66f8 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/ [...] 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 (f4cabb5ef32) \ 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 1828 -> 1884 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 33348 -> 32652 bytes 04-build_abe-stage1/console.log.xz | Bin 73804 -> 74424 bytes 06-build_abe-linux/console.log.xz | Bin 9068 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 246360 -> 244016 bytes 08-build_abe-stage2/console.log.xz | Bin 206212 -> 205512 bytes 09-build_abe-gdb/console.log.xz | Bin 40700 -> 39228 bytes 10-build_abe-qemu/console.log.xz | Bin 31036 -> 31028 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2964 -> 3068 bytes 13-check_regression/console.log.xz | Bin 6608 -> 7368 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 28 +- 13-check_regression/mail-body.txt | 155 +- 13-check_regression/results.compare | 56 +- 13-check_regression/results.compare2 | 87 +- 13-check_regression/results.regressions | 56 +- 14-update_baseline/console.log | 68 +- 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 | 157 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 56 +- sumfiles/g++.log.xz | Bin 3428088 -> 3410780 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 3012088 -> 3026984 bytes sumfiles/gcc.sum | 4491 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1041516 -> 1039544 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213848 -> 214416 bytes sumfiles/libgomp.sum | 19 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431888 -> 434856 bytes sumfiles/libstdc++.sum | 7 +- 43 files changed, 2701 insertions(+), 2647 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (40ce6485f36 -> 1bdba731b9c)

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 40ce6485f36 Daily bump. new 1bdba731b9c libbacktrace: rewrite and simplify main zstd loop 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: libbacktrace/elf.c | 948 +++++++++++++++++++++++++++++++++-------------------- 1 file changed, 592 insertions(+), 356 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch releases/gcc-12 updated (5ec102e3290 -> 3ee5a2371b2)

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 5ec102e3290 i386: fix assert (__builtin_cpu_supports ("x86-64") >= 0) new 3ee5a2371b2 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/ChangeLog | 20 ++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 7 +++++++ 3 files changed, 28 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch releases/gcc-11 updated (5d3bf022a7b -> 5539bdfc479)

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 5d3bf022a7b Daily bump. new 5539bdfc479 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, 5 months

[gcc] branch releases/gcc-10 updated (bd0033309c9 -> c89e7f8a711)

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 bd0033309c9 Daily bump. new c89e7f8a711 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, 5 months

[gcc] branch master updated (01254aa2eb7 -> 40ce6485f36)

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 01254aa2eb7 Fortran: ICE on recursive derived types with allocatable co [...] new 40ce6485f36 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: ChangeLog | 4 ++++ gcc/ChangeLog | 51 +++++++++++++++++++++++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/analyzer/ChangeLog | 36 ++++++++++++++++++++++++++++++++++ gcc/fortran/ChangeLog | 21 ++++++++++++++++++++ gcc/testsuite/ChangeLog | 25 ++++++++++++++++++++++++ libgomp/ChangeLog | 7 +++++++ libsanitizer/ChangeLog | 4 ++++ libstdc++-v3/ChangeLog | 24 +++++++++++++++++++++++ 9 files changed, 173 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (ed38cbc331e -> b813665fd2e)

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 binutils-gdb. from ed38cbc331e objdump: sframe: fix memory leaks new b813665fd2e Automatic date update in version.in 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: bfd/version.h | 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, 5 months

[binutils-gdb] branch gdb-12-branch updated (3f7f5a866f5 -> ed9b90db517)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-12-branch in repository binutils-gdb. from 3f7f5a866f5 Automatic date update in version.in new ed9b90db517 Automatic date update in version.in 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: bfd/version.h | 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, 5 months

[binutils-gdb] branch binutils-2_39-branch updated (32dfec072ae -> 6df169f352d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_39-branch in repository binutils-gdb. from 32dfec072ae Automatic date update in version.in new 6df169f352d Automatic date update in version.in 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: bfd/version.h | 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, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022