Merge `fabsf16/32/64/128` into `fabs::<F>` by N1ark · Pull Request #153834 · rust-lang/rust

N1ark · 2026-03-13T19:22:35Z

Following a small conversation on Zulip (and because I'd be interested in starting to contribute on Rust), I thought I'd give a try at merging the float intrinsics :)

This PR just merges fabsf16, fabsf32, fabsf64, fabsf128, as it felt like an easy first target.

Notes:

I'm opening the PR for one intrinsic as it's probably easier if the shift is done one intrinsic at a time, but let me know if you'd rather I do several at a time to reduce the number of PRs.
Currently this PR increases LOCs, despite being an attempt at simplifying the intrinsics/compilers. I believe this increase is a one time thing as I had to define new functions and move some things around, and hopefully future PRs/commits will reduce overall LoCs
fabsf32 and fabsf64 are #[rustc_intrinsic_const_stable_indirect], while fabsf16 and fabsf128 aren't; because f32/f64 expect the function to be const, the generic version must be made indirectly stable too. We'd need to check with T-lang this change is ok; the only other intrinsics where there is such a mismatch is minnum, maxnum and copysign.
I haven't touched libm because I'm not familiar with how it works; any guidance would be welcome!

rustbot · 2026-03-13T19:22:38Z

Some changes occurred to the CTFE machinery

cc @RalfJung, @oli-obk, @lcnr

Some changes occurred to the CTFE / Miri interpreter

cc @rust-lang/miri

Some changes occurred in compiler/rustc_codegen_gcc

cc @antoyo, @GuillaumeGomez

Some changes occurred in compiler/rustc_codegen_cranelift

cc @bjorn3

Some changes occurred to the intrinsics. Make sure the CTFE / Miri interpreter
gets adapted for the changes, if necessary.

cc @rust-lang/miri, @RalfJung, @oli-obk, @lcnr

rustbot · 2026-03-13T19:22:40Z

r? @TaKO8Ki

rustbot has assigned @TaKO8Ki.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

Owners of files modified in this PR: compiler
compiler expanded to 69 candidates
Random selection from 15 candidates

tgross35 · 2026-03-13T19:29:00Z

r? tgross35

N1ark · 2026-03-13T20:25:13Z

ah oops i was wondering why gcc wasn't working locally, guess it never installed :') ill fix this soon

scottmcm · 2026-03-13T20:41:52Z

library/core/src/intrinsics/mod.rs

-#[rustc_nounwind]
-#[rustc_intrinsic]
-pub const fn fabsf128(x: f128) -> f128;
+pub const fn fabs<T: Copy>(x: T) -> T;


suggestion: like there's

rust/library/core/src/intrinsics/bounds.rs

Lines 5 to 25 in f1ceedf

/// Types with a built-in dereference operator in runtime MIR,

/// aka references and raw pointers.

///

/// # Safety

/// Must actually *be* such a type.

pub unsafe trait BuiltinDeref: Sized {

type Pointee: PointeeSized;

}

unsafe impl<T: PointeeSized> BuiltinDeref for &mut T {

type Pointee = T;

}

unsafe impl<T: PointeeSized> BuiltinDeref for &T {

type Pointee = T;

}

unsafe impl<T: PointeeSized> BuiltinDeref for *mut T {

type Pointee = T;

}

unsafe impl<T: PointeeSized> BuiltinDeref for *const T {

type Pointee = T;

}

, consider adding a trait there just to help emphasize that this is for floats only, so this could be

Suggested change

pub const fn fabs<T: Copy>(x: T) -> T;

pub const fn fabs<T: bounds::FloatPrimitive>(x: T) -> T;

or similar.

Fixed in 74114c9; also added it to the other generic float intrinsics

note this changes the diagnostic when these intrinsics are misused: it now gives a type error (see 043f9ad) rather than a monomorphization error; i think this is a good thing :)

scottmcm · 2026-03-13T20:45:05Z

compiler/rustc_codegen_cranelift/src/intrinsics/mod.rs

+                ty::Float(FloatTy::F32) | ty::Float(FloatTy::F64) => fx.bcx.ins().fabs(x),
+                // FIXME(bytecodealliance/wasmtime#8312): Use `fabsf16` once Cranelift
+                // backend lowerings are implemented.
+                ty::Float(FloatTy::F16) => codegen_f16_f128::abs_f16(fx, x),


pondering: these make me wonder if it'd be worth just having fallback mir for this?

See how there's

pub const unsafe fn disjoint_bitor<T: [const] fallback::DisjointBitOr>(a: T, b: T) -> T {

for example to give that one a fallback; might be reasonable to do the same for fabs (since it's easy to implement) and backends can just fallback to that if they haven't implemented it natively for f16/f128 yet.

(That said, it's a copysign+fabs thing only, really, since fallback MIR for most float ops is probably not a good idea. fpow is hard.)

I'd like to have fallbacks for all of these via libcalls; have some of that in progress at #150946.

abs and copysign probably shouldn't use the libcalls though, they can copy the implementation from https://github.com/rust-lang/compiler-builtins/blob/85db9f1923007c287b894d392b880545ec70d05e/libm/src/math/generic/fabs.rs and https://github.com/rust-lang/compiler-builtins/blob/85db9f1923007c287b894d392b880545ec70d05e/libm/src/math/generic/copysign.rs.

compiler/rustc_codegen_llvm/src/intrinsic.rs

compiler/rustc_codegen_gcc/src/intrinsic/mod.rs

N1ark · 2026-03-14T11:30:16Z

btw; I saw in rustc_codegen_ssa there's two different errors relating to expecting float types; I picked BasicFloatType because in the same function BasicIntegerType is raised, but I'm curious if there's any reason to have both of these rather than merging them :) (FloatingPointType is only used in a couple places relating to SIMD intrinsics)

rust/compiler/rustc_codegen_ssa/src/errors.rs

Lines 718 to 724 in 620e36a

    
           #[diag("invalid monomorphization of `{$name}` intrinsic: expected basic float type, found `{$ty}`", code = E0511)] 
        
           BasicFloatType { 
        
               #[primary_span] 
        
               span: Span, 
        
               name: Symbol, 
        
               ty: Ty<'tcx>, 
        
           },

rust/compiler/rustc_codegen_ssa/src/errors.rs

Lines 742 to 748 in 620e36a

    
           #[diag("invalid monomorphization of `{$name}` intrinsic: `{$in_ty}` is not a floating-point type", code = E0511)] 
        
           FloatingPointType { 
        
               #[primary_span] 
        
               span: Span, 
        
               name: Symbol, 
        
               in_ty: Ty<'tcx>, 
        
           },

RalfJung · 2026-03-14T11:47:52Z

The diagnostic error types are quite the mess there, feel free to adjust or replace them by string-based errors if that simplifies the code.

N1ark · 2026-03-14T12:54:54Z

The diagnostic error types are quite the mess there, feel free to adjust or replace them by string-based errors if that simplifies the code.

fair enough :) removed the duplicate in ebb6dfb

scottmcm · 2026-03-15T03:13:20Z

I saw in rustc_codegen_ssa there's two different errors relating to expecting float types

Misuse of intrinsics falls under rust-lang/compiler-team#620 -- you can feel free to rip out any inconvenient errors entirely and just have them ICE.

library/core/src/intrinsics/mod.rs

compiler/rustc_const_eval/src/interpret/intrinsics.rs

RalfJung · 2026-03-15T10:52:53Z

library/core/src/intrinsics/mod.rs

-#[rustc_nounwind]
-#[rustc_intrinsic]
-pub const fn fabsf128(x: f128) -> f128;
+pub const fn fabs<T: bounds::FloatPrimitive>(x: T) -> T;


@rust-lang/lang this would mark fabs as indirectly const stable for all float types, not just f32 and f64. The const implementation is uniform across all types so I have no concerns about this -- the f16 and f128 implementation is and has been ready for stable for a while, it's the non-const implementation of f16 and f128 that's not ready. ;)

Nevertheless, new intrinsics being available to stable const code requires lang approval. Not sure if you think a full FCP is required for a trivial case like this.

btw if a FCP is required, we should throw in copysign in there, which is in the same situation: const stable for f32/f64 but not for f16/f128, and it's also a binary operation

We should probably throw in all the intrinsics you intend to generalize that are easily implemented with apfloat. Do you have a list of them?

Oh, I didn't realize all the f16/f128 rounding methods have already been allowed in const-stable since #143604. That may have been an accident, but it's also not really a problem.

yep, it's fabs, copysign, minnum and maxnum; all other float intrinsics are all const stable across all float types or not const stable for any

Personally (with my lang hat on but not speaking as team consensus) I would be fine treating this as "the previous FCP was saying that floating-point abs is allowed to be const-stable -- because it's easy to do reliably in const, being that it's only bitwise (without even NAN nondet, IIRC?) -- and how exactly that translates to specific intrinsics is a compiler/ctfe question without needing addtional lang FCPs".

But we'll see what the meeting says on Wed.

without even NAN nondet, IIRC?

Correct, fabs just mutates the sign bit and nothing else.

rustbot · 2026-03-16T00:38:59Z

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

tests/ui/intrinsics/bad-intrinsic-monomorphization.rs

compiler/rustc_codegen_llvm/src/intrinsic.rs

compiler/rustc_codegen_cranelift/src/intrinsics/mod.rs

tgross35 · 2026-03-16T20:52:13Z

compiler/rustc_codegen_cranelift/src/intrinsics/mod.rs

Cc @bjorn3 if you want to look at clif changes but this generally LGTM

compiler/rustc_codegen_gcc/src/intrinsic/mod.rs

tgross35

This needs the trivial lang approval for the intrinsics, and one more nit above. But aside from that, the changes here LGTM unless @RalfJung has anything else.

View changes since this review

Add `bounds::FloatPrimitive` Exhaustive float pattern match Fix GCC use span bugs

RalfJung · 2026-03-16T21:50:01Z

The const-eval parts LGTM.

traviscross · 2026-03-17T02:21:31Z

Makes sense and sounds good to me. Thanks @N1ark.

@rfcbot fcp merge lang

rust-rfcbot · 2026-03-17T02:21:34Z

Team member @traviscross has proposed to merge this. The next step is review by the rest of the tagged team members:

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

cc @rust-lang/lang-advisors: FCP proposed for lang, please feel free to register concerns.
See this document for info about what commands tagged team members can give me.

RalfJung · 2026-03-17T07:28:51Z

To be clear, the FCP covers doing this for fabs, copysign, minnum and maxnum. This PR only does the first step as that's easier for reviewing. (No other intrinsic has mixed const-stability across float types.)

That said, @scottmcm suggested we could consider this covered by the previous FCP for fabs on f32 and f64. We'll see what the meeting on Wed brings.

N1ark · 2026-03-17T10:04:15Z

(i should probably mention that since #153343 minnum and maxnum are named minimum_number_nsz and maximum_number_nsz)

nikomatsakis · 2026-03-18T15:11:49Z

@rfcbot reviewed

rust-rfcbot · 2026-03-18T15:12:13Z

🔔 This is now entering its final comment period, as per the review above. 🔔

rustbot assigned TaKO8Ki Mar 13, 2026

rustbot added the T-libs Relevant to the library team, which will review and decide on the PR/issue. label Mar 13, 2026

N1ark changed the title ~~Merge fabsfN into fabs::<F>~~ Merge fabsf16/32/64/128 into fabs::<F> Mar 13, 2026

rustbot assigned tgross35 and unassigned TaKO8Ki Mar 13, 2026

This comment has been minimized.

Sign in to view

scottmcm reviewed Mar 13, 2026

View reviewed changes

tgross35 reviewed Mar 13, 2026

View reviewed changes

compiler/rustc_codegen_llvm/src/intrinsic.rs Outdated Show resolved Hide resolved

tgross35 reviewed Mar 13, 2026

View reviewed changes

compiler/rustc_codegen_gcc/src/intrinsic/mod.rs Outdated Show resolved Hide resolved

This comment has been minimized.

Sign in to view

N1ark mentioned this pull request Mar 14, 2026

Cleanup handling of f128 intrinsics in GCC #153864

Closed

This comment has been minimized.

Sign in to view

N1ark force-pushed the generic-float-intrinsics branch from 69be112 to 9210d78 Compare March 14, 2026 12:50

This comment has been minimized.

Sign in to view

RalfJung reviewed Mar 15, 2026

View reviewed changes

library/core/src/intrinsics/mod.rs Outdated Show resolved Hide resolved

compiler/rustc_const_eval/src/interpret/intrinsics.rs Outdated Show resolved Hide resolved

compiler/rustc_const_eval/src/interpret/intrinsics.rs Show resolved Hide resolved

RalfJung reviewed Mar 15, 2026

View reviewed changes

RalfJung added the I-lang-nominated Nominated for discussion during a lang team meeting. label Mar 15, 2026

N1ark force-pushed the generic-float-intrinsics branch from 88a9639 to e21ccc5 Compare March 16, 2026 00:38

N1ark mentioned this pull request Mar 16, 2026

Make unary float intrinsics generic #153934

Draft

tgross35 reviewed Mar 16, 2026

View reviewed changes

tests/ui/intrinsics/bad-intrinsic-monomorphization.rs Show resolved Hide resolved

N1ark force-pushed the generic-float-intrinsics branch from e21ccc5 to 42c0625 Compare March 16, 2026 20:50

tgross35 reviewed Mar 16, 2026

View reviewed changes

N1ark force-pushed the generic-float-intrinsics branch from 42c0625 to 2fdefdf Compare March 16, 2026 21:12

tgross35 reviewed Mar 16, 2026

View reviewed changes

compiler/rustc_codegen_gcc/src/intrinsic/mod.rs Outdated Show resolved Hide resolved

tgross35 approved these changes Mar 16, 2026

View reviewed changes

N1ark added 2 commits March 16, 2026 21:49

Merge fabsfN into fabs::<F>

abb5228

Add `bounds::FloatPrimitive` Exhaustive float pattern match Fix GCC use span bugs

Remove InvalidMonomorphization::FloatingPointType

11c673b

N1ark force-pushed the generic-float-intrinsics branch from 2fdefdf to 11c673b Compare March 16, 2026 21:49

traviscross added the T-lang Relevant to the language team label Mar 17, 2026

rust-rfcbot added proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. labels Mar 17, 2026

traviscross added the P-lang-drag-1 Lang team prioritization drag level 1. https://rust-lang.zulipchat.com/#narrow/channel/410516-t-lang label Mar 18, 2026

rust-rfcbot added the final-comment-period In the final comment period and will be merged soon unless new substantive objections are raised. label Mar 18, 2026

rust-rfcbot removed the proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. label Mar 18, 2026

tgross35 added S-waiting-on-fcp Status: PR is in FCP and is awaiting for FCP to complete. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 22, 2026

	/// Types with a built-in dereference operator in runtime MIR,
	/// aka references and raw pointers.
	///
	/// # Safety
	/// Must actually be such a type.
	pub unsafe trait BuiltinDeref: Sized {
	type Pointee: PointeeSized;
	}

	unsafe impl<T: PointeeSized> BuiltinDeref for &mut T {
	type Pointee = T;
	}
	unsafe impl<T: PointeeSized> BuiltinDeref for &T {
	type Pointee = T;
	}
	unsafe impl<T: PointeeSized> BuiltinDeref for *mut T {
	type Pointee = T;
	}
	unsafe impl<T: PointeeSized> BuiltinDeref for *const T {
	type Pointee = T;
	}

	pub const fn fabs<T: Copy>(x: T) -> T;
	pub const fn fabs<T: bounds::FloatPrimitive>(x: T) -> T;

Uh oh!

Conversation

N1ark commented Mar 13, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rustbot commented Mar 13, 2026

Uh oh!

rustbot commented Mar 13, 2026

Uh oh!

tgross35 commented Mar 13, 2026

Uh oh!

This comment has been minimized.

N1ark commented Mar 13, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

N1ark Mar 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

This comment has been minimized.

N1ark commented Mar 14, 2026

Uh oh!

RalfJung commented Mar 14, 2026

Uh oh!

This comment has been minimized.

N1ark commented Mar 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment has been minimized.

This comment has been minimized.

scottmcm commented Mar 15, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

RalfJung Mar 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

N1ark Mar 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rustbot commented Mar 16, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

tgross35 left a comment • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

RalfJung commented Mar 16, 2026

Uh oh!

traviscross commented Mar 17, 2026

N1ark commented Mar 13, 2026 •

edited by rustbot

Loading

N1ark Mar 14, 2026 •

edited

Loading

N1ark commented Mar 14, 2026 •

edited

Loading

RalfJung Mar 15, 2026 •

edited

Loading

N1ark Mar 15, 2026 •

edited

Loading

tgross35 left a comment •

edited by rustbot

Loading

rust-rfcbot commented Mar 17, 2026 •

edited by scottmcm

Loading