Remove unsafe in core_arch/arm_shared/hint

.github/ISSUE_TEMPLATE/tracking_issue.md

@@ -1,26 +1,34 @@
 ---
 name: Tracking Issue
-about: A tracking issue for an accepted feature or RFC in Rust.
+about: A tracking issue for an unstable feature in Rust.
 title: Tracking Issue for XXX
 labels: C-tracking-issue
 ---
 <!--
 NOTE: For library features, please use the "Library Tracking Issue" template instead.
 
 Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
-feature from implementation to stabilisation. Make sure to include the relevant
-RFC for the feature if it has one. Otherwise provide a short summary of the
-feature and link any relevant PRs or issues, and remove any sections that are
-not relevant to the feature.
+feature from implementation to stabilisation.
 
 Remember to add team labels to the tracking issue.
-For a language team feature, this would e.g., be `T-lang`.
+For a language team feature, this would e.g., be `T-lang`:
+
+> @rustbot label T-lang
+
 Such a feature should also be labeled with e.g., `F-my_feature`.
 This label is used to associate issues (e.g., bugs and design questions) to the feature.
 -->
 
-This is a tracking issue for the RFC "XXX" (rust-lang/rfcs#NNN).
-The feature gate for the issue is `#![feature(FFF)]`.
+This is a tracking issue for `#![feature(FFF)]`.
+The RFC for this feature is rust-lang/rfcs#NNN.
+
+<!-- 
+Make sure to include the relevant RFC for the feature if it has one.
+
+Otherwise, provide a short summary and motivation of the
+feature and link any relevant PRs or issues.
+Remove any sections that are not relevant to the feature.
+-->
 
 ### About tracking issues
 
@@ -38,8 +46,8 @@ implementing a feature, followed by a PR that stabilises the feature. However
 for larger features an implementation could be broken up into multiple PRs.
 -->
 
-- [ ] Implement the RFC (cc @rust-lang/XXX -- can anyone write up mentoring
-      instructions?)
+- [ ] Create the feature gate
+- [ ] Implement the feature
 - [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
 - [ ] Style updates for any new syntax ([nightly-style-procedure])
   - [ ] Style team decision on new formatting
@@ -59,8 +67,8 @@ stabilised. It is useful to link related discussions and conculsions as they
 develop.
 -->
 
-- [ ] list all the "unresolved questions" found in the RFC to ensure they are
-  not forgotten.
+- [ ] List any unresolved questions, including those listed in the RFC if there is one,
+      to ensure they are not forgotten.
 
 ### Implementation history
 

.github/workflows/ci.yml

@@ -46,7 +46,7 @@ jobs:
   # If you want to modify CI jobs, take a look at src/ci/github-actions/jobs.yml.
   calculate_matrix:
     name: Calculate job matrix
-    runs-on: ubuntu-24.04-arm
+    runs-on: ubuntu-26.04-arm
     outputs:
       jobs: ${{ steps.jobs.outputs.jobs }}
       run_type: ${{ steps.jobs.outputs.run_type }}
@@ -309,7 +309,7 @@ jobs:
   # This job is used to publish toolstate for successful auto builds.
   outcome:
     name: publish toolstate
-    runs-on: ubuntu-24.04
+    runs-on: ubuntu-26.04
     needs: [ calculate_matrix, job ]
     if: ${{ needs.calculate_matrix.outputs.run_type == 'auto' }}
     environment: ${{ (github.repository == 'rust-lang/rust' && 'bors') || '' }}

.github/workflows/ghcr.yml

@@ -23,7 +23,7 @@ on:
 jobs:
   mirror:
     name: DockerHub mirror
-    runs-on: ubuntu-24.04
+    runs-on: ubuntu-26.04
     if: github.repository == 'rust-lang/rust'
     permissions:
       # Needed to write to the ghcr.io registry

.github/workflows/post-merge.yml

@@ -10,7 +10,7 @@ on:
 
 jobs:
   analysis:
-    runs-on: ubuntu-24.04
+    runs-on: ubuntu-26.04
     if: github.repository == 'rust-lang/rust'
     permissions:
       pull-requests: write

.mailmap

@@ -64,6 +64,7 @@ Arthur Cohen <arthur.cohen@epita.fr>
 Arthur Silva <arthurprs@gmail.com>
 Arthur Woimbée <arthur.woimbee@gmail.com>
 Artyom Pavlov <newpavlov@gmail.com>
+Austin K. <akiekintveld@icloud.com>
 Austin Seipp <mad.one@gmail.com> <as@hacks.yi.org>
 Ayaz Hafiz <ayaz.hafiz.1@gmail.com>
 Aydin Kim <ladinjin@hanmail.net> aydin.kim <aydin.kim@samsung.com>
@@ -144,6 +145,9 @@ Christian Poveda <git@pvdrz.com> <31802960+christianpoveda@users.noreply.github.
 Christian Poveda <git@pvdrz.com> <christianpoveda@uhura.edef.eu>
 Christian Vallentin <vallentinsource@gmail.com>
 Christoffer Buchholz <chris@chrisbuchholz.me>
+Clar Fon <usr@ltdk.xyz>
+Clar Fon <usr@ltdk.xyz> <clar@charr.xyz>
+Clar Fon <usr@ltdk.xyz> <them@lightdark.xyz>
 Clark Gaebel <cg.wowus.cg@gmail.com> <cgaebel@mozilla.com>
 Clement Miao <clementmiao@gmail.com>
 Clément Renault <renault.cle@gmail.com>
@@ -459,6 +463,8 @@ Mateusz Mikuła <oss@mateuszmikula.dev>
 Mateusz Mikuła <oss@mateuszmikula.dev> <mati865@gmail.com>
 Mateusz Mikuła <oss@mateuszmikula.dev> <mati865@users.noreply.github.com>
 Mateusz Mikuła <oss@mateuszmikula.dev> <matti@marinelayer.io>
+Matilde Morrone <contact@rosymati.com> <contact@matilde.pet>
+Matilde Morrone <contact@rosymati.com> <contact@morrone.dev>
 Matt Brubeck <mbrubeck@limpet.net> <mbrubeck@cs.hmc.edu>
 Matthew Auld <matthew.auld@intel.com>
 Matthew Jasper <mjjasper1@gmail.com>