diff options
| author | Chris Denton <chris@chrisdenton.dev> | 2025-04-22 15:24:06 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-22 15:24:06 +0000 |
| commit | 107f04daa81212e8973344a10e90a02d8d9e5eac (patch) | |
| tree | 26ef82d616c45636c037f813c6736aca755494a3 /compiler/rustc_codegen_llvm/src | |
| parent | c046a430d4b5c11f4e0d9c568f8f4d146d47c330 (diff) | |
| parent | 47a127884135771ae557eca71f964a5db655c2ea (diff) | |
| download | rust-107f04daa81212e8973344a10e90a02d8d9e5eac.tar.gz rust-107f04daa81212e8973344a10e90a02d8d9e5eac.zip | |
Rollup merge of #140072 - folkertdev:miri-fn-align, r=RalfJung
handle function alignment in miri tracking issue: https://github.com/rust-lang/rust/issues/82232 Fixes https://github.com/rust-lang/miri/issues/4282 The `#[repr(align(N))]` attribute on functions was ignored when using miri. For such a function, its address should be a multiple of `N`. There is some further discussion in the thread [#t-compiler/const-eval > function address alignment](https://rust-lang.zulipchat.com/#narrow/channel/146212-t-compiler.2Fconst-eval/topic/function.20address.20alignment) on how `dyn Fn` should be handled. The behavior there appears to be consistent between miri and nightly, though both may be incorrect. In any case, that can be resolved separately.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions