{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":565285932,"defaultBranch":"master","name":"rust","ownerLogin":"tgross35","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2022-11-12T22:50:03.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/13724985?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1725500575.0","currentOid":""},"activityList":{"items":[{"before":"5d8c94c9ff4c776a87647ec7367a832a8be2626e","after":"7f5149082a5624b7bf86acc09e058df01285ab90","ref":"refs/heads/cargo-update","pushedAt":"2024-09-11T02:01:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Adjust allowed dependencies from the latest `cargo update`","shortMessageHtmlLink":"Adjust allowed dependencies from the latest cargo update"}},{"before":"07c0585472a44be9c3370bd8579b9fd1af7714d9","after":"5d8c94c9ff4c776a87647ec7367a832a8be2626e","ref":"refs/heads/cargo-update","pushedAt":"2024-09-11T01:54:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Adjust allowed dependencies from the latest `cargo update`","shortMessageHtmlLink":"Adjust allowed dependencies from the latest cargo update"}},{"before":"61ab90e08b8fd46ed67b1897ce56e5046ab42908","after":"d5d83a8eb4531a07b6d5f90c65173d4915884e27","ref":"refs/heads/rollup-5qgpklj","pushedAt":"2024-09-05T01:42:59.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129653 - RalfJung:addr-of-read-only, r=scottmcm\n\nclarify that addr_of creates read-only pointers\n\nStacked Borrows does make this UB, but Tree Borrows does not. This is tied up with https://github.com/rust-lang/rust/issues/56604 and other UCG discussions. Also see [this collection of links](https://github.com/Rust-for-Linux/linux/pull/950#discussion_r1104759431) where rustc treats `addr_of!` as a \"non-mutating use\".\n\nSo, let's better be careful for now.","shortMessageHtmlLink":"Rollup merge of rust-lang#129653 - RalfJung:addr-of-read-only, r=scot…"}},{"before":"d2e15cf6a4f3455b95488ca4be82c248051f5c55","after":"61ab90e08b8fd46ed67b1897ce56e5046ab42908","ref":"refs/heads/rollup-5qgpklj","pushedAt":"2024-09-05T01:42:59.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129584 - lolbinarycat:old-upstream-warning, r=albertlarsan68\n\nwarn the user if the upstream master branch is old\n\nfixes https://github.com/rust-lang/rust/issues/129528","shortMessageHtmlLink":"Rollup merge of rust-lang#129584 - lolbinarycat:old-upstream-warning,…"}},{"before":"61cf52f384490b18d6c2126af11c0c95460d9c5e","after":"d2e15cf6a4f3455b95488ca4be82c248051f5c55","ref":"refs/heads/rollup-5qgpklj","pushedAt":"2024-09-05T01:42:58.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #128919 - Nadrieril:lint-query-leaks, r=cjgillot\n\nAdd an internal lint that warns when accessing untracked data\n\nSome methods access data that is not tracked by the query system and should be used with caution. As suggested in https://github.com/rust-lang/rust/pull/128815#issuecomment-2275488683, in this PR I propose a lint (modeled on the `potential_query_instability` lint) that warns when using some specially-annotatted functions.\n\nI can't tell myself if this lint would be that useful, compared to renaming `Steal::is_stolen` to `is_stolen_untracked`. This would depend on whether there are other functions we'd want to lint like this. So far it seems they're called `*_untracked`, which may be clear enough.\n\nr? `@oli-obk`","shortMessageHtmlLink":"Rollup merge of rust-lang#128919 - Nadrieril:lint-query-leaks, r=cjgi…"}},{"before":"af3be23e1163621b00c6e1b0fa148a328a2e3e5b","after":"61cf52f384490b18d6c2126af11c0c95460d9c5e","ref":"refs/heads/rollup-5qgpklj","pushedAt":"2024-09-05T01:42:58.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #128345 - sthibaul:hurd-amd64, r=Urgau\n\nadded support for GNU/Hurd on x86_64","shortMessageHtmlLink":"Rollup merge of rust-lang#128345 - sthibaul:hurd-amd64, r=Urgau"}},{"before":"f0de87670931a5f1543c49134cac4b935c87e9cc","after":"af3be23e1163621b00c6e1b0fa148a328a2e3e5b","ref":"refs/heads/rollup-5qgpklj","pushedAt":"2024-09-05T01:42:57.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #126136 - Noratrieb:bootstrap-naming, r=onur-ozkan\n\nCall the target libdir target libdir\n\nBecause it's the target libdir.\n\n`--print` uses the same terminology, and it's a simple way to make it obviously different from `$sysroot/lib`.","shortMessageHtmlLink":"Rollup merge of rust-lang#126136 - Noratrieb:bootstrap-naming, r=onur…"}},{"before":"1945e9fb4551c1b24851878a6c160f6390e3d352","after":"f0de87670931a5f1543c49134cac4b935c87e9cc","ref":"refs/heads/rollup-5qgpklj","pushedAt":"2024-09-05T01:42:57.000Z","pushType":"push","commitsCount":9,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #120736 - notriddle:notriddle/toc, r=t-rustdoc\n\nrustdoc: add header map to the table of contents\n\n## Summary\n\nAdd header sections to the sidebar TOC.\n\n### Preview\n\n\n\n* http://notriddle.com/rustdoc-html-demo-9/toc/rust/std/index.html\n* http://notriddle.com/rustdoc-html-demo-9/toc/rust-derive-builder/derive_builder/index.html\n\n## Motivation\n\nSome pages are very wordy, like these.\n\n| crate | word count |\n|--|--|\n| [std::option](https://doc.rust-lang.org/stable/std/option/index.html) | 2,138\n| [derive_builder](https://docs.rs/derive_builder/0.13.0/derive_builder/index.html) | 2,403\n| [tracing](https://docs.rs/tracing/0.1.40/tracing/index.html) | 3,912\n| [regex](https://docs.rs/regex/1.10.3/regex/index.html) | 8,412\n\nThis kind of very long document is more navigable with a table of contents, like Wikipedia's or the one [GitHub recently added](https://github.blog/changelog/2021-04-13-table-of-contents-support-in-markdown-files/) for READMEs.\n\nIn fact, the use case is so compelling, that it's been requested multiple times and implemented in an extension:\n\n* https://github.com/rust-lang/rust/issues/80858\n* https://github.com/rust-lang/rust/issues/28056\n* https://github.com/rust-lang/rust/issues/14475\n* https://rust.extension.sh/#show-table-of-content\n\n(Some of these issues ask for more than this, so don’t close them.)\n\nIt's also been implemented by hand in some crates, because the author really thought it was needed. Protip: for a more exhaustive list, run [`site:docs.rs table of contents`](https://duckduckgo.com/?t=ffab&q=site%3Adocs.rs+table+of+contents&ia=web), though some of them are false positives.\n\n* https://docs.rs/figment/0.10.14/figment/index.html#table-of-contents\n* https://docs.rs/csv/1.3.0/csv/tutorial/index.html#table-of-contents\n* https://docs.rs/axum/0.7.4/axum/response/index.html#table-of-contents\n* https://docs.rs/regex-automata/0.4.5/regex_automata/index.html#table-of-contents\n\nUnfortunately for these hand-built ToCs, because they're just part of the docs, there's no consistent way to turn them off if the reader doesn't want them. It's also more complicated to ensure they stay in sync with the docs they're supposed to describe, and they don't stay with you when you scroll like Wikipedia's [does now](https://uxdesign.cc/design-notes-on-the-2023-wikipedia-redesign-d6573b9af28d).\n\n## Guide-level explanation\n\nWhen writing docs for a top-level item, the first and second level of headers will be shown in an outline in the sidebar. In this context, \"top level\" means \"not associated\".\n\nThis means, if you're writing very long guides or explanations, and you want it to have a table of contents in the sidebar for its headings, the ideal place to attach it is usually the *module* or *crate*, because this page has fewer other things on it (and is the ideal place to describe \"cross-cutting concerns\" for its child items).\n\nIf you're reading documentation, and want to get rid of the table of contents, open the  Settings panel and checkmark \"Hide table of contents.\"\n\n## Reference-level explanation\n\nTop-level items have an outline generated. This works for potentially-malformed header trees by pairing a header with the nearest header with a higher level. For example:\n\n```markdown\n## A\n# B\n# C\n## D\n## E\n```\n\nA, B, and C are all siblings, and D and E are children of C.\n\nRustdoc only presents two layers of tree, but it tracks up to the full depth of 6 while preparing it.\n\nThat means that these two doc comment both generate the same outline:\n\n```rust\n/// # First\n/// ## Second\nstruct One;\n/// ## First\n/// ### Second\nstruct Two;\n```\n\n## Drawbacks\n\nThe biggest drawback is adding more stuff to the sidebar.\n\nMy crawl through docs.rs shows this to, surprisingly, be less of a problem than I thought. The manually-built tables of contents, and the pages with dozens of headers, usually seem to be modules or crates, not types (where extreme scrolling would become a problem, since they already have methods to deal with).\n\nThe best example of a type with many headers is [vec::Vec](https://doc.rust-lang.org/1.75.0/std/vec/struct.Vec.html), which still only has five headers, not dozens like [axum::extract](https://docs.rs/axum/0.7.4/axum/extract/index.html).\n\n## Rationale and alternatives\n\n### Why in the existing sidebar?\n\nThe method links and the top-doc header links have more in common with each other than either of them do with the \"In [parent module]\" links, and should go together.\n\n### Why limited to two levels?\n\nThe sidebar is pretty narrow, and I don't want too much space used by indentation. Making the sidebar wider, while it has some upsides, also takes up more space on middling-sized screens or tiled WMs.\n\n### Why not line wrap?\n\nThat behaves strangely when resizing.\n\n## Prior art\n\n### Doc generators that have TOC for headers\n\nhttps://hexdocs.pm/phoenix/Phoenix.Controller.html is very close, in the sense that it also has header sections directly alongside functions and types.\n\nAnother example, referenced as part of the [early sidebar discussion](https://github.com/rust-lang/rust/issues/37856) that added methods, Ruby will show a table of contents in the sidebar (for example, on the [ARGF](https://docs.ruby-lang.org/en/master/ARGF.html) class). According to their changelog, [they added it in 2013](https://github.com/ruby/rdoc/blob/06137bde8ccc48cd502bc28178bcd8f2dfe37624/History.rdoc#400--2013-02-24-).\n\nHaskell seems to mix text and functions even more freely than Elixir. For example, this [Naming conventions](https://hackage.haskell.org/package/base-4.19.0.0/docs/Control-Monad.html#g:3) is plain text, and is immediately followed by functions. And the [Pandoc top level](https://hackage.haskell.org/package/pandoc-3.1.11.1/docs/Text-Pandoc.html) has items split up by function, rather than by kind. Their TOC matches exactly with the contents of the page.\n\n### Doc generators that don't have header TOC, but still have headers\n\nElm, interestingly enough, seems to have the same setup that Rust used to have: sibling navigation between modules, and no index within a single page. [They keep Haskell's habit of named sections with machine-generated type signatures](https://package.elm-lang.org/packages/elm/browser/latest/Browser-Dom), though.\n\n[PHP](https://www.php.net/manual/en/book.datetime.php), like elm, also has a right-hand sidebar with sibling navigation. However, PHP has a single page for a single method, unlike Rust's page for an entire \"class.\" So even though these pages have headers, it's never more than ten at most. And when they have guides, those guides are also multi-page.\n\n## Unresolved questions\n\n* Writing recommendations for anyone who wants to take advantage of this.\n* Right now, it does not line wrap. That might be a bad idea: a lot of these are getting truncated.\n* Split sidebars, which I [tried implementing](https://rust-lang.zulipchat.com/#narrow/stream/266220-t-rustdoc/topic/Table.20of.20contents), are not required. The TOC can be turned off, if it's really a problem. Implemented in https://github.com/rust-lang/rust/pull/120818, but needs more, separate, discussion.\n\n## Future possibilities\n\nI would like to do a better job of distinguishing global navigation from local navigation. Rustdoc has a pretty reasonable information architecture, if only we did a better job of communicating it.\n\nThis PR aims, mostly, to help doc authors help their users by writing docs that can be more effectively skimmed. But it doesn't do anything to make it easier to tell the TOC and the Module Nav apart.","shortMessageHtmlLink":"Rollup merge of rust-lang#120736 - notriddle:notriddle/toc, r=t-rustdoc"}},{"before":"009e73825af0e59ad4fc603562e038b3dbd6593a","after":"1945e9fb4551c1b24851878a6c160f6390e3d352","ref":"refs/heads/rollup-5qgpklj","pushedAt":"2024-09-05T01:42:56.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #119229 - mati865:update-mingw-toolchain, r=jieyouxu,petrochenkov\n\nUpdate mingw-w64 + GNU toolchain\n\nThe list of packaged tools and their versions is available at: https://github.com/niXman/mingw-builds-binaries/releases/tag/14.1.0-rt_v12-rev0\n\nFixes: https://github.com/rust-lang/rust/issues/112368","shortMessageHtmlLink":"Rollup merge of rust-lang#119229 - mati865:update-mingw-toolchain, r=…"}},{"before":null,"after":"009e73825af0e59ad4fc603562e038b3dbd6593a","ref":"refs/heads/rollup-5qgpklj","pushedAt":"2024-09-05T01:42:55.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Auto merge of #129936 - matthiaskrgr:rollup-0s8xycb, r=matthiaskrgr\n\nRollup of 9 pull requests\n\nSuccessful merges:\n\n - #127692 (Suggest `impl Trait` for References to Bare Trait in Function Header)\n - #128701 (Don't Suggest Labeling `const` and `unsafe` Blocks )\n - #128934 (Non-exhaustive structs may be empty)\n - #129630 (Document the broken C ABI of `wasm32-unknown-unknown`)\n - #129863 (update comment regarding TargetOptions.features)\n - #129896 (do not attempt to prove unknowable goals)\n - #129926 (Move `SanityCheck` and `MirPass`)\n - #129928 (rustc_driver_impl: remove some old dead logic)\n - #129930 (include 1.80.1 release notes on master)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of rust-lang#129936 - matthiaskrgr:rollup-0s8xycb, r=matth…"}},{"before":"784cbd7beb60caf1d4f53e8c8ad346f95935efe3","after":"6aeb9b43f9cb9aac455a6390459c669939d110d2","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:28.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129939 - RalfJung:rvalue-len, r=compiler-errors\n\nexplain why Rvalue::Len still exists\n\nI just spent a bit of time trying to remove this until I realized why that's non-trivial. Let's document that for the next person. :)","shortMessageHtmlLink":"Rollup merge of rust-lang#129939 - RalfJung:rvalue-len, r=compiler-er…"}},{"before":"1b2a4de568bf29eb99fe5b929bf5a11a3dc302d8","after":"784cbd7beb60caf1d4f53e8c8ad346f95935efe3","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:28.000Z","pushType":"push","commitsCount":13,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129796 - GuillaumeGomez:unify-code-examples, r=notriddle\n\nUnify scraped examples with other code examples\n\nFixes #129763.\n\nThis first PR both fixes #129763 but also unifies buttons display for code examples:\n\n\n\nYou can test it [here](https://rustdoc.crud.net/imperio/unify-code-examples/doc/scrape_examples/fn.test.html) and [here](https://rustdoc.crud.net/imperio/unify-code-examples/doc/scrape_examples/fn.test_many.html).\n\nI'm planning to send a follow-up to make the buttons generated in JS directly (or I can do it in this PR directly if you prefer).\n\ncc ``@willcrichton``\nr? ``@notriddle``","shortMessageHtmlLink":"Rollup merge of rust-lang#129796 - GuillaumeGomez:unify-code-examples…"}},{"before":"f60debffd1215662030dc6c8ab716c302521479b","after":"1b2a4de568bf29eb99fe5b929bf5a11a3dc302d8","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:28.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129624 - tgross35:cargo-update, r=Mark-Simulacrum\n\nAdjust `memchr` pinning and run `cargo update`\n\ntry-job: x86_64-mingw","shortMessageHtmlLink":"Rollup merge of rust-lang#129624 - tgross35:cargo-update, r=Mark-Simu…"}},{"before":"8b5361e897145936f46a872fb565c505515c1e6c","after":"f60debffd1215662030dc6c8ab716c302521479b","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:27.000Z","pushType":"push","commitsCount":8,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129529 - lqd:stable-new-solver, r=Kobzol\n\nAdd test to build crates used by r-a on stable\n\nr? ```@Kobzol```\n\nI've opened other PRs for this one to work and they've landed already. I cherry-picked your commit, and added the last remaining pieces we needed I think.","shortMessageHtmlLink":"Rollup merge of rust-lang#129529 - lqd:stable-new-solver, r=Kobzol"}},{"before":"5f10e04d1675ac586b6be2fd2f3a863b325be138","after":"8b5361e897145936f46a872fb565c505515c1e6c","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:27.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129471 - GuillaumeGomez:sort-impl-associated-items, r=t-rustdoc-frontend\n\n[rustdoc] Sort impl associated items by kinds and then by appearance\n\nFollowing [this zulip discussion](https://rust-lang.zulipchat.com/#narrow/stream/266220-t-rustdoc/topic/.22Freeze.22.20order.20of.20items.20in.20.28trait.29.20impls.3F), I implemented it.\n\nThis brings the following change: impl associated items will now be grouped by kind and will now be first sorted by kind and then by the order they are declared in the source code (like currently).\n\nThe kinds are sorted in the following order:\n1. Constants\n2. Types\n3. Functions\n\nThe reason behind this order is that associated constants can be used in associated types (like length in arrays) and both associated types and associated constants can be used in associated functions. So if an associated item from the same impl is used, its definition will always be above where it's being used.\n\ncc ``@camelid``\nr? ``@notriddle``","shortMessageHtmlLink":"Rollup merge of rust-lang#129471 - GuillaumeGomez:sort-impl-associate…"}},{"before":"f393f8623e08bfce933878c8bc98755d23a08508","after":"5f10e04d1675ac586b6be2fd2f3a863b325be138","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:26.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #128871 - onur-ozkan:128180, r=Kobzol\n\nbypass linker configuration and cross target check for specific commands\n\nAvoids configuring the linker and checking cross-target-specific tools unless necessary.\n\nResolves #128180\n\ncc ```@ChrisDenton```","shortMessageHtmlLink":"Rollup merge of rust-lang#128871 - onur-ozkan:128180, r=Kobzol"}},{"before":"add2bcca91f5e85081e035995de87838f189bfde","after":"f393f8623e08bfce933878c8bc98755d23a08508","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:26.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #127021 - thesummer:1-add-target-support-for-rtems-arm-xilinx-zedboard, r=tgross35\n\nAdd target support for RTEMS Arm\n\n# `armv7-rtems-eabihf`\n\nThis PR adds a new target for the RTEMS RTOS. To get things started it focuses on Xilinx/AMD Zynq-based targets, but in theory it should also support other armv7-based board support packages in the future.\nGiven that RTEMS has support for many POSIX functions it is mostly enabling corresponding unix features for the new target.\nI also previously started a PR in libc (https://github.com/rust-lang/libc/pull/3561) to add the needed OS specific C-bindings and was told that a PR in this repo is needed first. I will update the PR to the newest version after approval here.\nI will probably also need to change one line in the backtrace repo.\n\nCurrent status is that I could compile rustc for the new target locally (with the updated libc and backtrace) and could compile binaries, link, and execute a simple \"Hello World\" RTEMS application for the target hardware.\n\n> A proposed target or target-specific patch that substantially changes code shared with other targets (not just target-specific code) must be reviewed and approved by the appropriate team for that shared code before acceptance.\n\nThere should be no breaking changes for existing targets. Main changes are adding corresponding `cfg` switches for the RTEMS OS and adding the C binding in libc.\n\n# Tier 3 target policy\n\n> - A tier 3 target must have a designated developer or developers (the \"target maintainers\") on record to be CCed when issues arise regarding the target. (The mechanism to track and CC such developers may evolve over time.)\n\nI will do the maintenance (for now) further members of the RTEMS community will most likely join once the first steps have been done.\n\n> - Targets must use naming consistent with any existing targets; for instance, a target for the same CPU or OS as an existing Rust target should use the same name for that CPU or OS. Targets should normally use the same names and naming conventions as used elsewhere in the broader ecosystem beyond Rust (such as in other toolchains), unless they have a very good reason to diverge. Changing the name of a target can be highly disruptive, especially once the target reaches a higher tier, so getting the name right is important even for a tier 3 target.\n> - Target names should not introduce undue confusion or ambiguity unless absolutely necessary to maintain ecosystem compatibility. For example, if the name of the target makes people extremely likely to form incorrect beliefs about what it targets, the name should be changed or augmented to disambiguate it.\n> - If possible, use only letters, numbers, dashes and underscores for the name. Periods (`.`) are known to cause issues in Cargo.\n\nThe proposed triple is `armv7-rtems-eabihf`\n\n> - Tier 3 targets may have unusual requirements to build or use, but must not create legal issues or impose onerous legal terms for the Rust project or for Rust developers or users.\n> - The target must not introduce license incompatibilities.\n> - Anything added to the Rust repository must be under the standard Rust license (`MIT OR Apache-2.0`).\n> - The target must not cause the Rust tools or libraries built for any other host (even when supporting cross-compilation to the target) to depend on any new dependency less permissive than the Rust licensing policy. This applies whether the dependency is a Rust crate that would require adding new license exceptions (as specified by the `tidy` tool in the rust-lang/rust repository), or whether the dependency is a native library or binary. In other words, the introduction of the target must not cause a user installing or running a version of Rust or the Rust tools to be subject to any new license requirements.\n> - Compiling, linking, and emitting functional binaries, libraries, or other code for the target (whether hosted on the target itself or cross-compiling from another target) must not depend on proprietary (non-FOSS) libraries. Host tools built for the target itself may depend on the ordinary runtime libraries supplied by the platform and commonly used by other applications built for the target, but those libraries must not be required for code generation for the target; cross-compilation to the target must not require such libraries at all. For instance, `rustc` built for the target may depend on a common proprietary C runtime library or console output library, but must not depend on a proprietary code generation library or code optimization library. Rust's license permits such combinations, but the Rust project has no interest in maintaining such combinations within the scope of Rust itself, even at tier 3.\n> - \"onerous\" here is an intentionally subjective term. At a minimum, \"onerous\" legal/licensing terms include but are _not_ limited to: non-disclosure requirements, non-compete requirements, contributor license agreements (CLAs) or equivalent, \"non-commercial\"/\"research-only\"/etc terms, requirements conditional on the employer or employment of any particular Rust developers, revocable terms, any requirements that create liability for the Rust project or its developers or users, or any requirements that adversely affect the livelihood or prospects of the Rust project or its developers or users.\n\nThe tools consists of the cross-compiler toolchain (gcc-based). The RTEMS kernel (BSD license) and parts of the driver stack of FreeBSD (BSD license). All tools are FOSS and publicly available here: https://gitlab.rtems.org/rtems\nThere are also no new features or dependencies introduced to the Rust code.\n\n> - Neither this policy nor any decisions made regarding targets shall create any binding agreement or estoppel by any party. If any member of an approving Rust team serves as one of the maintainers of a target, or has any legal or employment requirement (explicit or implicit) that might affect their decisions regarding a target, they must recuse themselves from any approval decisions regarding the target's tier status, though they may otherwise participate in discussions.\n\nN/A to me. I am not a reviewer nor Rust team member.\n\n> - Tier 3 targets should attempt to implement as much of the standard libraries as possible and appropriate (`core` for most targets, `alloc` for targets that can support dynamic memory allocation, `std` for targets with an operating system or equivalent layer of system-provided functionality), but may leave some code unimplemented (either unavailable or stubbed out as appropriate), whether because the target makes it impossible to implement or challenging to implement. The authors of pull requests are not obligated to avoid calling any portions of the standard library on the basis of a tier 3 target not implementing those portions.\n\n`core` and `std` compile. Some advanced features of the `std` lib might not work yet. However, the goal of this tier 3 target it to make it easier for other people to build and run test applications to better identify the unsupported features and work towards enabling them.\n\n> - The target must provide documentation for the Rust community explaining how to build for the target, using cross-compilation if possible. If the target supports running binaries, or running tests (even if they do not pass), the documentation must explain how to run such binaries or tests for the target, using emulation if possible or dedicated hardware if necessary.\n\nBuilding is described in platform support doc. Running simple unit tests works. Running the test suite of the stdlib is currently not that easy. Trying to work towards that after the this target has been added to the nightly.\n\n> - Tier 3 targets must not impose burden on the authors of pull requests, or other developers in the community, to maintain the target. In particular, do not post comments (automated or manual) on a PR that derail or suggest a block on the PR based on a tier 3 target. Do not send automated messages or notifications (via any medium, including via ```@`)`` to a PR author or others involved with a PR regarding a tier 3 target, unless they have opted into such messages.\n\nUnderstood.\n\n> - Backlinks such as those generated by the issue/PR tracker when linking to an issue or PR are not considered a violation of this policy, within reason. However, such messages (even on a separate repository) must not generate notifications to anyone involved with a PR who has not requested such notifications.\n\nOk\n\n> - Patches adding or updating tier 3 targets must not break any existing tier 2 or tier 1 target, and must not knowingly break another tier 3 target without approval of either the compiler team or the maintainers of the other tier 3 target.\n> - In particular, this may come up when working on closely related targets, such as variations of the same architecture with different features. Avoid introducing unconditional uses of features that another variation of the target may not have; use conditional compilation or runtime detection, as appropriate, to let each target run code supported by that target.\n\nI think, I didn't add any breaking changes for any existing targets (see the comment regarding features above).\n\n> - Tier 3 targets must be able to produce assembly using at least one of rustc's supported backends from any host target.\n\nCan produce assembly code via the llvm backend (tested on Linux).\n\n>\n> If a tier 3 target stops meeting these requirements, or the target maintainers no longer have interest or time, or the target shows no signs of activity and has not built for some time, or removing the target would improve the quality of the Rust codebase, we may post a PR to remove it; any such PR will be CCed to the target maintainers (and potentially other people who have previously worked on the target), to check potential interest in improving the situation.GIAt this tier, the Rust project provides no official support for a target, so we place minimal requirements on the introduction of targets.\n\nUnderstood.\n\nr? compiler-team","shortMessageHtmlLink":"Rollup merge of rust-lang#127021 - thesummer:1-add-target-support-for…"}},{"before":"d6c8169c186ab16a3404cd0d0866674018e8a19e","after":"add2bcca91f5e85081e035995de87838f189bfde","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:25.000Z","pushType":"push","commitsCount":8,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #101339 - the8472:ci-randomize-debug, r=Mark-Simulacrum\n\nenable -Zrandomize-layout in debug CI builds\n\nThis builds rustc/libs/tools with `-Zrandomize-layout` on *-debug CI runners.\n\nOnly a handful of tests and asserts break with that enabled, which is promising. One test was fixable, the rest is dealt with by disabling them through new cargo features or compiletest directives.\n\nThe config.toml flag `rust.randomize-layout` defaults to false, so it has to be explicitly enabled for now.","shortMessageHtmlLink":"Rollup merge of rust-lang#101339 - the8472:ci-randomize-debug, r=Mark…"}},{"before":null,"after":"d6c8169c186ab16a3404cd0d0866674018e8a19e","ref":"refs/heads/rollup-352zljc","pushedAt":"2024-09-04T03:12:24.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Auto merge of #129922 - matthiaskrgr:rollup-4vqx8ct, r=matthiaskrgr\n\nRollup of 8 pull requests\n\nSuccessful merges:\n\n - #129152 (custom/external clippy support for bootstrapping)\n - #129311 (don't copy `.rustc-dev-contents` from CI rustc)\n - #129800 (Move the Windows remove_dir_all impl into a module and make it more race resistant)\n - #129860 (update `object` dependency to remove duplicate `wasmparser`)\n - #129885 (chore: remove repetitive words)\n - #129913 (Add missing read_buf stub for x86_64-unknown-l4re-uclibc)\n - #129916 (process.rs: remove \"Basic usage\" text where not useful)\n - #129917 (Fix parsing of beta version in dry-run mode)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of rust-lang#129922 - matthiaskrgr:rollup-4vqx8ct, r=matth…"}},{"before":"a57c399cec91f691a997f8c610b115cb8c673b17","after":"07c0585472a44be9c3370bd8579b9fd1af7714d9","ref":"refs/heads/cargo-update","pushedAt":"2024-09-03T16:22:51.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Adjust allowed dependencies from the latest `cargo update`","shortMessageHtmlLink":"Adjust allowed dependencies from the latest cargo update"}},{"before":"a0073104ad92fe07e9174b47125da19c64fcf621","after":null,"ref":"refs/heads/triagebot-vacation","pushedAt":"2024-09-02T16:33:31.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"}},{"before":"5321ba80e9463384f784eef57e9df338d0be2413","after":"a57c399cec91f691a997f8c610b115cb8c673b17","ref":"refs/heads/cargo-update","pushedAt":"2024-09-01T06:58:40.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Adjust allowed dependencies from the latest `cargo update`","shortMessageHtmlLink":"Adjust allowed dependencies from the latest cargo update"}},{"before":"47c2f976e91e8ad7eee0be56f949642621ade71a","after":"5321ba80e9463384f784eef57e9df338d0be2413","ref":"refs/heads/cargo-update","pushedAt":"2024-09-01T02:39:52.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Adjust allowed dependencies from the latest `cargo update`","shortMessageHtmlLink":"Adjust allowed dependencies from the latest cargo update"}},{"before":null,"after":"a0073104ad92fe07e9174b47125da19c64fcf621","ref":"refs/heads/triagebot-vacation","pushedAt":"2024-09-01T02:25:00.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Mark myself as on vacation for triagebot","shortMessageHtmlLink":"Mark myself as on vacation for triagebot"}},{"before":"3636530ac277026f4067e042d4e34784bf5ef03a","after":"483c6436b4510225a3ccb9e3eb744aa9ccfa5784","ref":"refs/heads/f16-format-parse","pushedAt":"2024-09-01T02:22:35.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Add slow test file","shortMessageHtmlLink":"Add slow test file"}},{"before":"2b78d920964e1d70927bcd208529bda0e11120d0","after":"0d634185dfddefe09047881175f35c65d68dcff1","ref":"refs/heads/master","pushedAt":"2024-08-30T20:18:19.000Z","pushType":"push","commitsCount":1950,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Auto merge of #129750 - GuillaumeGomez:rollup-gphsb7y, r=GuillaumeGomez\n\nRollup of 7 pull requests\n\nSuccessful merges:\n\n - #123940 (debug-fmt-detail option)\n - #128166 (Improved `checked_isqrt` and `isqrt` methods)\n - #128970 (Add `-Zlint-llvm-ir`)\n - #129316 (riscv64imac: allow shadow call stack sanitizer)\n - #129690 (Add `needs-unwind` compiletest directive to `libtest-thread-limit` and replace some `Path` with `path` in `run-make`)\n - #129732 (Add `unreachable_pub`, round 3)\n - #129743 (Fix rustdoc clippy lints)\n\nr? `@ghost`\n`@rustbot` modify labels: rollup","shortMessageHtmlLink":"Auto merge of rust-lang#129750 - GuillaumeGomez:rollup-gphsb7y, r=Gui…"}},{"before":"404089ffcee795c5008fd2eb97ef0f0429243434","after":"3636530ac277026f4067e042d4e34784bf5ef03a","ref":"refs/heads/f16-format-parse","pushedAt":"2024-08-30T09:04:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"dec2flt: Refactor the slow module","shortMessageHtmlLink":"dec2flt: Refactor the slow module"}},{"before":"75ae913ec000753bc34efd8b37cf2a4b26f13041","after":null,"ref":"refs/heads/rollup-jume49s","pushedAt":"2024-08-27T09:44:29.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"}},{"before":"8ea70e9537f0e22c2eb32eabc08175093617fb16","after":"75ae913ec000753bc34efd8b37cf2a4b26f13041","ref":"refs/heads/rollup-jume49s","pushedAt":"2024-08-27T06:46:53.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129559 - RalfJung:float-nan-semantics, r=thomcc\n\nfloat types: document NaN bit pattern guarantees\n\nPart of https://github.com/rust-lang/rust/issues/128288: document the guarantees we make for NaN bit patterns.\n\nCc ``@tgross35``","shortMessageHtmlLink":"Rollup merge of rust-lang#129559 - RalfJung:float-nan-semantics, r=th…"}},{"before":"3c131a3f54c6ebe4dd8edac0236655996dfb2c51","after":"8ea70e9537f0e22c2eb32eabc08175093617fb16","ref":"refs/heads/rollup-jume49s","pushedAt":"2024-08-27T06:46:53.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"tgross35","name":"Trevor Gross","path":"/tgross35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/13724985?s=80&v=4"},"commit":{"message":"Rollup merge of #129536 - beetrees:f16-f128-inline-asm-aarch64, r=Amanieu\n\nAdd `f16` and `f128` inline ASM support for `aarch64`\n\nAdds `f16` and `f128` inline ASM support for `aarch64`. SIMD vector types are taken from [the ARM intrinsics list](https://developer.arm.com/architectures/instruction-sets/intrinsics/#f:`@navigationhierarchiesreturnbasetype=[float]&f:@navigationhierarchieselementbitsize=[16]&f:@navigationhierarchiesarchitectures=[A64]).` Based on the work of `@lengrongfu` in #127043.\n\nRelevant issue: #125398\nTracking issue: #116909\n\n`@rustbot` label +F-f16_and_f128\n\ntry-job: aarch64-gnu\ntry-job: aarch64-apple","shortMessageHtmlLink":"Rollup merge of rust-lang#129536 - beetrees:f16-f128-inline-asm-aarch…"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0xMVQwMjowMTozOS4wMDAwMDBazwAAAASyrlTq","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0xMVQwMjowMTozOS4wMDAwMDBazwAAAASyrlTq","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOC0yN1QwNjo0Njo1My4wMDAwMDBazwAAAASlA8I5"}},"title":"Activity · tgross35/rust"}