{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":349102039,"defaultBranch":"master","name":"rust","ownerLogin":"durin42","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2021-03-18T14:21:46.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/20269?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1713380876.0","currentOid":""},"activityList":{"items":[{"before":"a0581b5b7fe6b9add5c1f0fe90a9f2cc8249b01e","after":"cfe3f77f9dd83bceb35e9685c4690b7b1a5be1b0","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-05-23T19:23:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_gcc: fix changed method signature","shortMessageHtmlLink":"rustc_codegen_gcc: fix changed method signature"}},{"before":"3ea494190f0df0e6d1454b160419c9a72cfca5ba","after":"a0581b5b7fe6b9add5c1f0fe90a9f2cc8249b01e","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-05-23T19:10:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"cleanup: run rustfmt","shortMessageHtmlLink":"cleanup: run rustfmt"}},{"before":"ad0ef0c1bee62b77b448d46ef135ad1f3a60a1ad","after":"3ea494190f0df0e6d1454b160419c9a72cfca5ba","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-05-23T19:08:49.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"cleanup: standardize on summary over index in names\n\nI did this in the user-facing logic, but I noticed while fixing a minor\ndefect that I had missed it in a few places in the internal details.","shortMessageHtmlLink":"cleanup: standardize on summary over index in names"}},{"before":"01c1ffd340cbd500eb49e2277bffdc2d16968eec","after":"ad0ef0c1bee62b77b448d46ef135ad1f3a60a1ad","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-05-22T16:41:46.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"cleanup: remove leftover extra block\n\nThis was needed in an older version of this patch, but never got edited\nout when it became obsolete.","shortMessageHtmlLink":"cleanup: remove leftover extra block"}},{"before":"c34660e4851a837c46eab53dcc3c5ed3dff44cb2","after":"01c1ffd340cbd500eb49e2277bffdc2d16968eec","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-05-21T14:28:54.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.indexing.o -c foo.c` and then get both foo.o\n(full of bitcode) and foo.indexing.o (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.\n\nI talked some to @teresajohnson about naming in this area, as things\nseem to be a little confused between various blog posts and build\nsystems. \"bitcode index\" and \"bitcode summary\" tend to be a little too\nambiguous, and she tends to use \"thin link bitcode\" and \"minimized\nbitcode\" (which matches the descriptions in LLVM). Since the clang\noption is thin-link-bitcode, I went with that to try and not add a new\nspelling in the world.\n\nPer @dtolnay, you can work around the lack of this by using `lld\n--thinlto-index-only` to do the indexing on regular .o files of\nbitcode, but that is a bit wasteful on actions when we already have all\nthe information in rustc and could just write out the matching minimized\nbitcode. I didn't test that at all in our infrastructure, because by the\ntime I learned that I already had this patch largely written.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"74ad3bdf3625ee6ad6242bbd4447c7bd5d01a368","after":"c34660e4851a837c46eab53dcc3c5ed3dff44cb2","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-05-20T21:44:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.indexing.o -c foo.c` and then get both foo.o\n(full of bitcode) and foo.indexing.o (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.\n\nI talked some to @teresajohnson about naming in this area, as things\nseem to be a little confused between various blog posts and build\nsystems. \"bitcode index\" and \"bitcode summary\" tend to be a little too\nambiguous, and she tends to use \"thin link bitcode\" and \"minimized\nbitcode\" (which matches the descriptions in LLVM). Since the clang\noption is thin-link-bitcode, I went with that to try and not add a new\nspelling in the world.\n\nPer @dtolnay, you can work around the lack of this by using `lld\n--thinlto-index-only` to do the indexing on regular .o files of\nbitcode, but that is a bit wasteful on actions when we already have all\nthe information in rustc and could just write out the matching minimized\nbitcode. I didn't test that at all in our infrastructure, because by the\ntime I learned that I already had this patch largely written.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"3b8ddedd03edf793ddd0f03ffd676496df7f83e2","after":"74ad3bdf3625ee6ad6242bbd4447c7bd5d01a368","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-05-20T20:11:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.indexing.o -c foo.c` and then get both foo.o\n(full of bitcode) and foo.indexing.o (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.\n\nI talked some to @teresajohnson about naming in this area, as things\nseem to be a little confused between various blog posts and build\nsystems. \"bitcode index\" and \"bitcode summary\" tend to be a little too\nambiguous, and she tends to use \"thin link bitcode\" and \"minimized\nbitcode\" (which matches the descriptions in LLVM). Since the clang\noption is thin-link-bitcode, I went with that to try and not add a new\nspelling in the world.\n\nPer @dtolnay, you can work around the lack of this by using `lld\n--thinlto-index-only` to do the indexing on regular .o files of\nbitcode, but that is a bit wasteful on actions when we already have all\nthe information in rustc and could just write out the matching minimized\nbitcode. I didn't test that at all in our infrastructure, because by the\ntime I learned that I already had this patch largely written.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"39e41aef5ec37d24b43f4f69dcf28e114570b288","after":"3b8ddedd03edf793ddd0f03ffd676496df7f83e2","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-04-30T19:10:48.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.indexing.o -c foo.c` and then get both foo.o\n(full of bitcode) and foo.indexing.o (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.\n\nI talked some to @teresajohnson about naming in this area, as things\nseem to be a little confused between various blog posts and build\nsystems. \"bitcode index\" and \"bitcode summary\" tend to be a little too\nambiguous, and she tends to use \"thin link bitcode\" and \"minimized\nbitcode\" (which matches the descriptions in LLVM). Since the clang\noption is thin-link-bitcode, I went with that to try and not add a new\nspelling in the world.\n\nPer @dtolnay, you can work around the lack of this by using `lld\n--thinlto-index-only` to reconstruct an index from regular .o files of\nbitcode, but that is a bit wasteful on actions when we already have all\nthe information in rustc and could just write out the matching file. I\ndidn't test that at all in our infrastructure, because by the time I\nlearned that I already had this patch largely written.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"125c9f22546c3ab880274eaa417d6e3abff983f7","after":"39e41aef5ec37d24b43f4f69dcf28e114570b288","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-04-30T19:09:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.indexing.o -c foo.c` and then get both foo.o\n(full of bitcode) and foo.indexing.o (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.\n\nI talked some to @teresajohnson about naming in this area, as things\nseem to be a little confused between various blog posts and build\nsystems. \"bitcode index\" and \"bitcode summary\" tend to be a little too\nambiguous, and she tends to use \"thin link bitcode\" and \"minimized\nbitcode\" (which matches the descriptions in LLVM). Since the clang\noption is thin-link-bitcode, I went with that to try and not add a new\nspelling in the world.\n\nPer @dtolnay, you can work around the lack of this by using `lld\n--thinlto-index-only` to reconstruct an index from regular .o files of\nbitcode, but that is a bit wasteful on actions when we already have all\nthe information in rustc and could just write out the matching file. I\ndidn't test that at all in our infrastructure, because by the time I\nlearned that I already had this patch largely written.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"b3dd8f30d6ee8ee4a36cd1efe73822b57eef18d3","after":"125c9f22546c3ab880274eaa417d6e3abff983f7","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-04-30T19:00:33.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.indexing.o -c foo.c` and then get both foo.o\n(full of bitcode) and foo.indexing.o (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.\n\nI talked some to @teresajohnson about naming in this area, as things\nseem to be a little confused between various blog posts and build\nsystems. \"bitcode index\" and \"bitcode summary\" tend to be a little too\nambiguous, and she tends to use \"thin link bitcode\" and \"minimized\nbitcode\" (which matches the descriptions in LLVM). Since the clang\noption is thin-link-bitcode, I went with that to try and not add a new\nspelling in the world.\n\nPer @dtolnay, you can work around the lack of this by using `lld\n--thinlto-index-only` to reconstruct an index from regular .o files of\nbitcode, but that is a bit wasteful on actions when we already have all\nthe information in rustc and could just write out the matching file. I\ndidn't test that at all in our infrastructure, because by the time I\nlearned that I already had this patch largely written.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"7b853554edeed1b3957fe6914dc54d4f1dd370f3","after":"22b704bac4779d773cf9e641c0b0c3e17352dc3a","ref":"refs/heads/llvm-19-riscv-feature","pushedAt":"2024-04-17T20:15:32.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"llvm: update riscv target feature to match LLVM 19\n\nIn llvm/llvm-project@9067070d91e9d8cdd8509ffa56a076f08a3d7281 they ended\nup largely reverting\nllvm/llvm-project@e81796671890b59c110f8e41adc7ca26f8484d20. This means\nthe change we did in\nrust-lang/rust@b378059e6b2573c5356423fa31d184a89a3b6029 is now only\ncorrct for LLVM 18...so we have to adjust again.\n\n@rustbot label: +llvm-main","shortMessageHtmlLink":"llvm: update riscv target feature to match LLVM 19"}},{"before":"f3ff6e2461d76dcfebe4103c531658f60148040d","after":"7b853554edeed1b3957fe6914dc54d4f1dd370f3","ref":"refs/heads/llvm-19-riscv-feature","pushedAt":"2024-04-17T19:19:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"llvm: update riscv target feature to match LLVM 19\n\nIn llvm/llvm-project@9067070d91e9d8cdd8509ffa56a076f08a3d7281 they ended\nup largely reverting\nllvm/llvm-project@e81796671890b59c110f8e41adc7ca26f8484d20. This means\nthe change we did in\nrust-lang/rust@b378059e6b2573c5356423fa31d184a89a3b6029 is now only\ncorrct for LLVM 18...so we have to adjust again.\n\n@rustbot label: +llvm-main","shortMessageHtmlLink":"llvm: update riscv target feature to match LLVM 19"}},{"before":"c1b8eb9e112d76aa97eead3a7794fd36b156d922","after":"f3ff6e2461d76dcfebe4103c531658f60148040d","ref":"refs/heads/llvm-19-riscv-feature","pushedAt":"2024-04-17T19:09:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"llvm: update riscv target feature to match LLVM 19\n\nIn llvm/llvm-project@9067070d91e9d8cdd8509ffa56a076f08a3d7281 they ended\nup largely reverting\nllvm/llvm-project@e81796671890b59c110f8e41adc7ca26f8484d20. This means\nthe change we did in\nrust-lang/rust@b378059e6b2573c5356423fa31d184a89a3b6029 is now only\ncorrct for LLVM 18...so we have to adjust again.\n\n@rustbot label: +llvm-main","shortMessageHtmlLink":"llvm: update riscv target feature to match LLVM 19"}},{"before":null,"after":"c1b8eb9e112d76aa97eead3a7794fd36b156d922","ref":"refs/heads/llvm-19-riscv-feature","pushedAt":"2024-04-17T19:07:56.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"llvm: update riscv target feature to match LLVM 19\n\nIn llvm/llvm-project@9067070d91e9d8cdd8509ffa56a076f08a3d7281 they ended\nup largely reverting\nllvm/llvm-project@e81796671890b59c110f8e41adc7ca26f8484d20. This means\nthe change we did in\nrust-lang/rust@b378059e6b2573c5356423fa31d184a89a3b6029 is now only\ncorrct for LLVM 18...so we have to adjust again.\n\n@rustbot label: +llvm-main","shortMessageHtmlLink":"llvm: update riscv target feature to match LLVM 19"}},{"before":null,"after":"b3dd8f30d6ee8ee4a36cd1efe73822b57eef18d3","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-04-12T15:09:06.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.thinlto.bc -c foo.c` and then get both foo.o\n(full of bitcode) and foo.thinlto.bc (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"f8daa7d4f6c13ca12f3074ee2ba4f9866a6f8bee","after":null,"ref":"refs/heads/llvm-delete-dead-zext-code","pushedAt":"2024-04-12T15:08:55.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"7568ccb877777b2d984420e041d3cd9d5e08bb13","after":null,"ref":"refs/heads/llvm-header-vectorizer-removal","pushedAt":"2024-04-12T15:08:54.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"5d8d700fd3911b8219168b3a9bdac52691fd5a42","after":null,"ref":"refs/heads/nneg-zext","pushedAt":"2024-04-12T15:08:53.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"58fdbd1479e13de780832ee549e631cfa1deb3a0","after":null,"ref":"refs/heads/overaligned-constant","pushedAt":"2024-04-12T15:08:52.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"ca274a90f9d8dcc5ea7924a4d60d59aee3739833","after":null,"ref":"refs/heads/llvm-19-moar-noalias","pushedAt":"2024-04-12T15:08:46.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"b3dd8f30d6ee8ee4a36cd1efe73822b57eef18d3","after":null,"ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-04-12T15:08:39.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"9d1bd2e067a82d6a2552b3705bbe6f256e9bde0c","after":null,"ref":"refs/heads/llvm-19-pgo-coldfuncopt","pushedAt":"2024-04-12T15:08:36.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"09a159601c52a9619b4bb948b578123aa4ebf5ef","after":null,"ref":"refs/heads/llvm-19-writeImportLibrary","pushedAt":"2024-04-12T15:08:36.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"ef626d772f7ee9ddba526b0693993f6479ee5c14","after":null,"ref":"refs/heads/llvm-19-compression-options","pushedAt":"2024-04-12T15:08:35.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"2a0107496ec22c63f313e39482377a4189cce904","after":null,"ref":"refs/heads/llvm-19-pass-ptr","pushedAt":"2024-04-12T15:08:33.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}},{"before":"4d14a87263946b8f9e021ccffee9a2e8e6f019f5","after":"b3dd8f30d6ee8ee4a36cd1efe73822b57eef18d3","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-04-12T15:07:59.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.thinlto.bc -c foo.c` and then get both foo.o\n(full of bitcode) and foo.thinlto.bc (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"7db4a89d49a8ed3a5f79b6cc3d555696baa1bbc3","after":"6bb6b816bfcf9e26fac5175e3e907dcefe5ecdbc","ref":"refs/heads/master","pushedAt":"2024-04-12T15:07:52.000Z","pushType":"push","commitsCount":10000,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"Auto merge of #122046 - Nadrieril:integrate-or-pats2, r=matthewjasper\n\nmatch lowering: handle or-patterns one layer at a time\n\n`create_or_subcandidates` and `merge_trivial_subcandidates` both call themselves recursively to handle nested or-patterns, which is hard to follow. In this PR I avoid the need for that; we now process a single \"layer\" of or-patterns at a time.\n\nBy calling back into `match_candidates`, we only need to expand one layer at a time. Conversely, since we always try to simplify a layer that we just expanded (thanks to https://github.com/rust-lang/rust/pull/123067), we only have to merge one layer at a time.\n\nr? `@matthewjasper`","shortMessageHtmlLink":"Auto merge of <a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2170191850\" data-permission-text=\"Title is private\" data-url=\"https://github.com/rust-lang/rust/issues/122046\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/rust-lang/rust/pull/122046/hovercard\" href=\"https://github.com/rust-lang/rust/pull/122046\">rust-lang#122046</a> - Nadrieril:integrate-or-pats2, r=matt…"}},{"before":null,"after":"2a0107496ec22c63f313e39482377a4189cce904","ref":"refs/heads/llvm-19-pass-ptr","pushedAt":"2024-03-26T18:11:38.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"RustWrapper: update call for llvm/llvm-project@44d037cc258dcf179d2c48c93996bb406ecd0fae\n\nEasy change.\n\n@rustbot label: +llvm-main","shortMessageHtmlLink":"RustWrapper: update call for <a class=\"commit-link\" data-hovercard-type=\"commit\" data-hovercard-url=\"https://github.com/llvm/llvm-project/commit/44d037cc258dcf179d2c48c93996bb406ecd0fae/hovercard\" href=\"https://github.com/llvm/llvm-project/commit/44d037cc258dcf179d2c48c93996bb406ecd0fae\">llvm/llvm-project@<tt>44d037c</tt></a>"}},{"before":"74eba7392b64b326e2135041195ab40553ffeb1f","after":"4d14a87263946b8f9e021ccffee9a2e8e6f019f5","ref":"refs/heads/thin-link-bitcode","pushedAt":"2024-03-22T18:42:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"},"commit":{"message":"rustc_codegen_llvm: add support for writing summary bitcode\n\nTypical uses of ThinLTO don't have any use for this as a standalone\nfile, but distributed ThinLTO uses this to make the linker phase more\nefficient. With clang you'd do something like `clang -flto=thin\n-fthin-link-bitcode=foo.thinlto.bc -c foo.c` and then get both foo.o\n(full of bitcode) and foo.thinlto.bc (just the summary or index part of\nthe bitcode). That's then usable by a two-stage linking process that's\nmore friendly to distributed build systems like bazel, which is why I'm\nworking on this area.","shortMessageHtmlLink":"rustc_codegen_llvm: add support for writing summary bitcode"}},{"before":"3982a24b3a31b105d7edff25134c03dbe3aaad11","after":null,"ref":"refs/heads/emit-llvm-summary","pushedAt":"2024-03-22T18:41:34.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"durin42","name":"Augie Fackler","path":"/durin42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20269?s=80&v=4"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEUmDSYAA","startCursor":null,"endCursor":null}},"title":"Activity · durin42/rust"}