rust/compiler/rustc_smir/src, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-07-14T09:25:54+00:00rename `stable_mir` to `rustc_public`, and `rustc_smir` to `rustc_public_bridge`2025-07-14T09:25:54+00:00Makaim4kai410@gmail.com2025-07-12T15:28:50+00:00urn:sha1:6598c61725abb0e8179b8a5fab7a0ed1f7fcaf5fAuto merge of #143182 - xdoardo:more-addrspace, r=workingjubilee2025-07-07T17:28:14+00:00borsbors@rust-lang.org2025-07-07T17:28:14+00:00urn:sha1:2f8eeb2bba86b8f457ec602c578473c711f85628
Allow custom default address spaces and parse `p-` specifications in the datalayout string
Some targets, such as CHERI, use as default an address space different from the "normal" default address space `0` (in the case of CHERI, [200 is used](https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-877.pdf)). Currently, `rustc` does not allow to specify custom address spaces and does not take into consideration [`p-` specifications in the datalayout string](https://llvm.org/docs/LangRef.html#langref-datalayout).
This patch tries to mitigate these problems by allowing targets to define a custom default address space (while keeping the default value to address space `0`) and adding the code to parse the `p-` specifications in `rustc_abi`. The main changes are that `TargetDataLayout` now uses functions to refer to pointer-related informations, instead of having specific fields for the size and alignment of pointers in the default address space; furthermore, the two `pointer_size` and `pointer_align` fields in `TargetDataLayout` are replaced with an `FxHashMap` that holds info for all the possible address spaces, as parsed by the `p-` specifications.
The potential performance drawbacks of not having ad-hoc fields for the default address space will be tested in this PR's CI run.
r? workingjubilee
compiler: Parse `p-` specs in datalayout string, allow definition of custom default data address space2025-07-07T07:04:53+00:00Edoardo Marangoniedoardo.marangoni@scisemi.com2025-06-29T10:11:51+00:00urn:sha1:93f1201c0616672d71e640a0ad600d029448c40amove `stable_mir` back to its own crate and move `rustc_internal` to the`stable_mir` crate2025-07-06T12:25:42+00:00Makaim4kai410@gmail.com2025-07-05T15:28:03+00:00urn:sha1:c42a9ac6029e8a2b6b76564240e1f89850992b21
As part of this reorganization, some traits need to be moved from `rustc_smir::context::traits` to `stable_mir::unstable::internal_cx`. These traits are specifically designed for `InternalCx` to clarify the behavior of different functions that share the same name. This move is necessary to avoid orphan rule violations.
Same for types2025-07-04T18:26:09+00:00Michael Gouletmichael@errs.io2025-04-11T04:25:25+00:00urn:sha1:74570e526e6816b04c479a34dc1f2116e121e798Remove Symbol for Named LateParam/Bound variants2025-07-04T18:14:22+00:00Michael Gouletmichael@errs.io2025-04-11T04:17:19+00:00urn:sha1:42c9bfd2b96f2e6cd0e4e6fab21c2d5499883089refactor: implement a new bridge trait `Allocation`2025-07-04T01:57:47+00:00Makaim4kai410@gmail.com2025-06-25T16:27:54+00:00urn:sha1:e26ae60be37be8303f956971925ac440b1cf0e71refactor: rewrite `adt_repr()`, `adt_discr_for_variant()` and `coroutine_discr_for_variant()`2025-07-04T01:57:47+00:00Makaim4kai410@gmail.com2025-06-21T10:40:14+00:00urn:sha1:854292d589098ab4de4934cdcdcc886e77a5b1d7refactor: don't use rustc_type_ir directly2025-07-04T01:57:47+00:00Makaim4kai410@gmail.com2025-06-21T10:33:02+00:00urn:sha1:b7be9cd151290250d74c7ccedda00ce9b11c6a44refactor: avoid calling internal functions in `predicates_of()` and `explicit_predicates_of()`2025-07-04T01:57:46+00:00Makaim4kai410@gmail.com2025-06-09T08:26:12+00:00urn:sha1:e3f2096849c9e5a8fe725c26a6e53906f8bfffdc