- "object 64ef8f2c4791940d7f3945507b6a45c20d959260\ntype commit\ntag powerpc-5.9-3\ntagger Michael Ellerman <mpe@ellerman.id.au> 1598185676 +1000\n\npowerpc fixes for 5.9 #3\n\nAdd perf support for emitting extended registers for power10.\n\nA fix for CPU hotplug on pseries, where on large/loaded systems we may not wait\nlong enough for the CPU to be offlined, leading to crashes.\n\nAddition of a raw cputable entry for Power10, which is not required to boot, but\nis required to make our PMU setup work correctly in guests.\n\nThree fixes for the recent changes on 32-bit Book3S to move modules into their\nown segment for strict RWX.\n\nA fix for a recent change in our powernv PCI code that could lead to crashes.\n\nA change to our perf interrupt accounting to avoid soft lockups when using some\nevents, found by syzkaller.\n\nA change in the way we handle power loss events from the hypervisor on pseries.\nWe no longer immediately shut down if we're told we're running on a UPS.\n\nA few other minor fixes.\n\nThanks to:\n Alexey Kardashevskiy, Andreas Schwab, Aneesh Kumar K.V, Anju T Sudhakar,\n Athira Rajeev, Christophe Leroy, Frederic Barrat, Greg Kurz, Kajol Jain,\n Madhavan Srinivasan, Michael Neuling, Michael Roth, Nageswara R Sastry, Oliver\n O'Halloran, Thiago Jung Bauermann, Vaidyanathan Srinivasan, Vasant Hegde.\n-----BEGIN PGP SIGNATURE-----\n\niQJHBAABCAAxFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAl9CYMwTHG1wZUBlbGxl\ncm1hbi5pZC5hdQAKCRBR6+o8yOGlgC/wEACljEVnfHzUObmIgqn9Ru3JlfEI6Hlk\nts7kajCgS/I/bV6DoDMZ8rlZX87QFOwiBkNM1I+vGHSLAuzsmFAnbFPyxw/idxpQ\nXUoNy8OCvbbzCPzChYdiU0PxW2h2i+QxkmktlWSN1SAPudJUWvoPS2Y4+sC4zksk\nB4B6tbW2DT8TFO1kKeZsU9r2t+EH5KwlIOi+uxbH8d76lJINKkBNSnjzMytl7drM\nTZx/HWr8+s/WJo1787x6bv8gxs5tV9b4vIKt2YZNTY2kvYsEDE+fBR1XfCAneXMw\nASYnZV+/xCLIUpRF6DI4RAShLBT/Sfiy1yMTndZgfqAgquokFosszNx2zrk0IzCd\nAgqX93YGbGz/H72W3Y/B0W9+74XyO/u2D9zhNpkCRMpdcsM5MbvOQrQA5Ustu47E\nav5MOaF/nNCd8J+OC4Qjgt5VFb/s0h4FdtrwT80srOa2U6Of9cD/T6xAfOszSJ96\ncWdSb5qhn5wuD9pP32KjwdmWBiUw38/gnRGKpRlOVzyHL/GKZijyaBbWBlkoEmty\n0nbjWW/IVfsOb5Weuiybg541h/QOVuOkb2pOvPClITiH83MY/AciDJ+auo4M//hW\nhaKz9IgV/KctmzDE+v9d0BD8sGmW03YUcQAPdRufI0eGXijDLcnHeuk2B3Nu84Pq\n8mtev+VQ+T6cZA==\n=sdJ1\n-----END PGP SIGNATURE-----"
- "message": "Merge tag 'powerpc-5.9-3' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux\n\nPull powerpc fixes from Michael Ellerman:\n\n - Add perf support for emitting extended registers for power10.\n\n - A fix for CPU hotplug on pseries, where on large/loaded systems we\n may not wait long enough for the CPU to be offlined, leading to\n crashes.\n\n - Addition of a raw cputable entry for Power10, which is not required\n to boot, but is required to make our PMU setup work correctly in\n guests.\n\n - Three fixes for the recent changes on 32-bit Book3S to move modules\n into their own segment for strict RWX.\n\n - A fix for a recent change in our powernv PCI code that could lead to\n crashes.\n\n - A change to our perf interrupt accounting to avoid soft lockups when\n using some events, found by syzkaller.\n\n - A change in the way we handle power loss events from the hypervisor\n on pseries. We no longer immediately shut down if we're told we're\n running on a UPS.\n\n - A few other minor fixes.\n\nThanks to Alexey Kardashevskiy, Andreas Schwab, Aneesh Kumar K.V, Anju T\nSudhakar, Athira Rajeev, Christophe Leroy, Frederic Barrat, Greg Kurz,\nKajol Jain, Madhavan Srinivasan, Michael Neuling, Michael Roth,\nNageswara R Sastry, Oliver O'Halloran, Thiago Jung Bauermann,\nVaidyanathan Srinivasan, Vasant Hegde.\n\n* tag 'powerpc-5.9-3' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:\n powerpc/perf/hv-24x7: Move cpumask file to top folder of hv-24x7 driver\n powerpc/32s: Fix module loading failure when VMALLOC_END is over 0xf0000000\n powerpc/pseries: Do not initiate shutdown when system is running on UPS\n powerpc/perf: Fix soft lockups due to missed interrupt accounting\n powerpc/powernv/pci: Fix possible crash when releasing DMA resources\n powerpc/pseries/hotplug-cpu: wait indefinitely for vCPU death\n powerpc/32s: Fix is_module_segment() when MODULES_VADDR is defined\n powerpc/kasan: Fix KASAN_SHADOW_START on BOOK3S_32\n powerpc/fixmap: Fix the size of the early debug area\n powerpc/pkeys: Fix build error with PPC_MEM_KEYS disabled\n powerpc/kernel: Cleanup machine check function declarations\n powerpc: Add POWER10 raw mode cputable entry\n powerpc/perf: Add extended regs support for power10 platform\n powerpc/perf: Add support for outputting extended regs in perf intr_regs\n powerpc: Fix P10 PVR revision in /proc/cpuinfo for SMT4 cores\n",
+ "content/sha1_git:61d3c9e1157203f0c4ed5165608d92294eaca808/raw/": "# The Rust Programming Language\n\nThis is the main source code repository for [Rust]. It contains the compiler,\nstandard library, and documentation.\n\n[Rust]: https://www.rust-lang.org\n\n## Quick Start\n\nRead [\"Installation\"] from [The Book].\n\n[\"Installation\"]: https://doc.rust-lang.org/book/ch01-01-installation.html\n[The Book]: https://doc.rust-lang.org/book/index.html\n\n## Installing from Source\n\n_Note: If you wish to contribute to the compiler, you should read [this\nchapter][rustcguidebuild] of the rustc-guide instead of this section._\n\nThe Rust build system has a Python script called `x.py` to bootstrap building\nthe compiler. More information about it may be found by running `./x.py --help`\nor reading the [rustc guide][rustcguidebuild].\n\n[rustcguidebuild]: https://rust-lang.github.io/rustc-guide/building/how-to-build-and-run.html\n\n### Building on *nix\n1. Make sure you have installed the dependencies:\n\n * `g++` 5.1 or later or `clang++` 3.5 or later\n * `python` 2.7 (but not 3.x)\n * GNU `make` 3.81 or later\n * `cmake` 3.4.3 or later\n * `curl`\n * `git`\n * `ssl` which comes in `libssl-dev` or `openssl-devel`\n * `pkg-config` if you are compiling on Linux and targeting Linux\n\n2. Clone the [source] with `git`:\n\n ```sh\n $ git clone https://github.com/rust-lang/rust.git\n $ cd rust\n ```\n\n[source]: https://github.com/rust-lang/rust\n\n3. Configure the build settings:\n\n The Rust build system uses a file named `config.toml` in the root of the\n source tree to determine various configuration settings for the build.\n Copy the default `config.toml.example` to `config.toml` to get started.\n\n ```sh\n $ cp config.toml.example config.toml\n ```\n\n It is recommended that if you plan to use the Rust build system to create\n an installation (using `./x.py install`) that you set the `prefix` value\n in the `[install]` section to a directory that you have write permissions.\n\n Create install directory if you are not installing in default directory\n\n4. Build and install:\n\n ```sh\n $ ./x.py build && ./x.py install\n ```\n\n When complete, `./x.py install` will place several programs into\n `$PREFIX/bin`: `rustc`, the Rust compiler, and `rustdoc`, the\n API-documentation tool. This install does not include [Cargo],\n Rust's package manager. To build and install Cargo, you may\n run `./x.py install cargo` or set the `build.extended` key in\n `config.toml` to `true` to build and install all tools.\n\n[Cargo]: https://github.com/rust-lang/cargo\n\n### Building on Windows\n\nThere are two prominent ABIs in use on Windows: the native (MSVC) ABI used by\nVisual Studio, and the GNU ABI used by the GCC toolchain. Which version of Rust\nyou need depends largely on what C/C++ libraries you want to interoperate with:\nfor interop with software produced by Visual Studio use the MSVC build of Rust;\nfor interop with GNU software built using the MinGW/MSYS2 toolchain use the GNU\nbuild.\n\n#### MinGW\n\n[MSYS2][msys2] can be used to easily build Rust on Windows:\n\n[msys2]: https://msys2.github.io/\n\n1. Grab the latest [MSYS2 installer][msys2] and go through the installer.\n\n2. Run `mingw32_shell.bat` or `mingw64_shell.bat` from wherever you installed\n MSYS2 (i.e. `C:\\msys64`), depending on whether you want 32-bit or 64-bit\n Rust. (As of the latest version of MSYS2 you have to run `msys2_shell.cmd\n -mingw32` or `msys2_shell.cmd -mingw64` from the command line instead)\n\n3. From this terminal, install the required tools:\n\n ```sh\n # Update package mirrors (may be needed if you have a fresh install of MSYS2)\n $ pacman -Sy pacman-mirrors\n\n # Install build tools needed for Rust. If you're building a 32-bit compiler,\n # then replace \"x86_64\" below with \"i686\". If you've already got git, python,\n # or CMake installed and in PATH you can remove them from this list. Note\n # that it is important that you do **not** use the 'python2' and 'cmake'\n # packages from the 'msys2' subsystem. The build has historically been known\n # to fail with these packages.\n $ pacman -S git \\\n make \\\n diffutils \\\n tar \\\n mingw-w64-x86_64-python2 \\\n mingw-w64-x86_64-cmake \\\n mingw-w64-x86_64-gcc\n ```\n\n4. Navigate to Rust's source code (or clone it), then build it:\n\n ```sh\n $ ./x.py build && ./x.py install\n ```\n\n#### MSVC\n\nMSVC builds of Rust additionally require an installation of Visual Studio 2017\n(or later) so `rustc` can use its linker. The simplest way is to get the\n[Visual Studio], check the “C++ build tools” and “Windows 10 SDK” workload.\n\n[Visual Studio]: https://visualstudio.microsoft.com/downloads/\n\n(If you're installing cmake yourself, be careful that “C++ CMake tools for\nWindows” doesn't get included under “Individual components”.)\n\nWith these dependencies installed, you can build the compiler in a `cmd.exe`\nshell with:\n\n```sh\n> python x.py build\n```\n\nCurrently, building Rust only works with some known versions of Visual Studio. If\nyou have a more recent version installed the build system doesn't understand\nthen you may need to force rustbuild to use an older version. This can be done\nby manually calling the appropriate vcvars file before running the bootstrap.\n\n```batch\n> CALL \"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Auxiliary\\Build\\vcvars64.bat\"\n> python x.py build\n```\n\n### Building rustc with older host toolchains\nIt is still possible to build Rust with the older toolchain versions listed below, but only if the\nLLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN option is set to true in the config.toml file.\n\n* Clang 3.1\n* Apple Clang 3.1\n* GCC 4.8\n* Visual Studio 2015 (Update 3)\n\nToolchain versions older than what is listed above cannot be used to build rustc.\n\n#### Specifying an ABI\n\nEach specific ABI can also be used from either environment (for example, using\nthe GNU ABI in PowerShell) by using an explicit build triple. The available\nWindows build triples are:\n- GNU ABI (using GCC)\n - `i686-pc-windows-gnu`\n - `x86_64-pc-windows-gnu`\n- The MSVC ABI\n - `i686-pc-windows-msvc`\n - `x86_64-pc-windows-msvc`\n\nThe build triple can be specified by either specifying `--build=<triple>` when\ninvoking `x.py` commands, or by copying the `config.toml` file (as described\nin [Installing From Source](#installing-from-source)), and modifying the\n`build` option under the `[build]` section.\n\n### Configure and Make\n\nWhile it's not the recommended build system, this project also provides a\nconfigure script and makefile (the latter of which just invokes `x.py`).\n\n```sh\n$ ./configure\n$ make && sudo make install\n```\n\nWhen using the configure script, the generated `config.mk` file may override the\n`config.toml` file. To go back to the `config.toml` file, delete the generated\n`config.mk` file.\n\n## Building Documentation\n\nIf you’d like to build the documentation, it’s almost the same:\n\n```sh\n$ ./x.py doc\n```\n\nThe generated documentation will appear under `doc` in the `build` directory for\nthe ABI used. I.e., if the ABI was `x86_64-pc-windows-msvc`, the directory will be\n`build\\x86_64-pc-windows-msvc\\doc`.\n\n## Notes\n\nSince the Rust compiler is written in Rust, it must be built by a\nprecompiled \"snapshot\" version of itself (made in an earlier stage of\ndevelopment). As such, source builds require a connection to the Internet, to\nfetch snapshots, and an OS that can execute the available snapshot binaries.\n\nSnapshot binaries are currently built and tested on several platforms:\n\n| Platform / Architecture | x86 | x86_64 |\n|----------------------------|-----|--------|\n| Windows (7, 8, 10, ...) | ✓ | ✓ |\n| Linux (2.6.18 or later) | ✓ | ✓ |\n| macOS (10.7 Lion or later) | ✓ | ✓ |\n\nYou may find that other platforms work, but these are our officially\nsupported build environments that are most likely to work.\n\nThere is more advice about hacking on Rust in [CONTRIBUTING.md].\n\n[CONTRIBUTING.md]: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md\n\n## Getting Help\n\nThe Rust community congregates in a few places:\n\n* [Stack Overflow] - Direct questions about using the language.\n* [users.rust-lang.org] - General discussion and broader questions.\n* [/r/rust] - News and general discussion.\n\n[Stack Overflow]: https://stackoverflow.com/questions/tagged/rust\n[/r/rust]: https://reddit.com/r/rust\n[users.rust-lang.org]: https://users.rust-lang.org/\n\n## Contributing\n\nTo contribute to Rust, please see [CONTRIBUTING](CONTRIBUTING.md).\n\nMost real-time collaboration happens in a variety of channels on the\n[Rust Discord server][rust-discord], with channels dedicated for getting help,\ncommunity, documentation, and all major contribution areas in the Rust ecosystem.\nA good place to ask for help would be the #help channel.\n\nThe [rustc guide] might be a good place to start if you want to find out how\nvarious parts of the compiler work.\n\nAlso, you may find the [rustdocs for the compiler itself][rustdocs] useful.\n\n[rust-discord]: https://discord.gg/rust-lang\n[rustc guide]: https://rust-lang.github.io/rustc-guide/about-this-guide.html\n[rustdocs]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc/\n\n## License\n\nRust is primarily distributed under the terms of both the MIT license\nand the Apache License (Version 2.0), with portions covered by various\nBSD-like licenses.\n\nSee [LICENSE-APACHE](LICENSE-APACHE), [LICENSE-MIT](LICENSE-MIT), and\n[COPYRIGHT](COPYRIGHT) for details.\n\n## Trademark\n\nThe Rust programming language is an open source, community project governed\nby a core team. It is also sponsored by the Mozilla Foundation (“Mozilla”),\nwhich owns and protects the Rust and Cargo trademarks and logos\n(the “Rust Trademarks”).\n\nIf you want to use these names or brands, please read the [media guide][media-guide].\n\nThird-party logos may be subject to third-party copyrights and trademarks. See\n[Licenses][policies-licenses] for details.\n\n[media-guide]: https://www.rust-lang.org/policies/media-guide\n[policies-licenses]: https://www.rust-lang.org/policies/licenses\n",
+ "message": "Auto merge of #69854 - pietroalbini:stable-next, r=Centril\n\n[stable] Release 1.42.0\n\nThis PR prepares the release artifacts of Rust 1.42.0, and cherry-picks the following PRs:\n\n* https://github.com/rust-lang/rust/pull/69754: Update deprecation version to 1.42 for Error::description\n* https://github.com/rust-lang/rust/pull/69753: Do not ICE when matching an uninhabited enum's field\n* https://github.com/rust-lang/rust/pull/69522 / https://github.com/rust-lang/rust/pull/69853: error_derive_forbidden_on_non_adt: be more graceful\n* https://github.com/rust-lang/rust/pull/68598: Fix null synthetic_implementors error\n\nIn addition, the release notes are updated to include the remaining compatibility notes.\n\nr? @Centril\n",
+ "message": "Auto merge of #69748 - Mark-Simulacrum:beta-next, r=Mark-Simulacrum\n\n[beta] another round of backports for 1.42\n\nThis backports the following pull requests:\n\n* Fix a leak in `DiagnosticBuilder::into_diagnostic`. #69628\n* stash API: remove panic to fix ICE. #69623\n* Do not ICE on invalid type node after parse recovery #69583\n* Backport only: avoid ICE on bad placeholder type #69324\n* add regression test for issue #68794 #69168\n* Update compiler-builtins to 0.1.25 #69086\n* Update RELEASES.md for 1.42.0 #68989\n",
+ "message": "Renumber listings following removed listing\n\nListing 20-21 was removed in 37a17ef40ccee85b28963cfe8d83ff8d66bd7717,\nand listing 20-22 was renumbered because it's in the same file as 20-21\nwas, but the rest of the listings in chapter 20 weren't renumbered.\n",
+ "message": "Merge #218\n\n218: fixed typo in Interrupts.md r=therealprof a=tessi\n\nJust fixing a double-`to` I encountered while reading the book.\r\nThanks for the great content ❤️ \n\nCo-authored-by: Philipp Tessenow <philipp@tessenow.org>\n",
+ "message": "Remove mention of contravariance possibly getting scrapped\n\nContravariance is part of stable Rust, and it's a natural outcome of how\n`fn(T)` interacts with lifetimes, so it's hard to imagine this ever\ngoing away.\n\ntl;dr: LONG LIVE CONTRAVARIANCE!\n",
+ "message": 'CamelCase -> UpperCamelCase\n\nThe compiler will raise a warning unless it is UpperCamelCase. Since the warning is explicit about mentioning "upper", maybe the guide should too?',