Most targets, like arm and amd64 don't support fast float to ulong conversion.
The value isn't used for the managed crypto code and is still validfor CryptoAPI, but if it changes Mono can't find keypairs made with earlier versions. Fixes #31199
The check from  is fine when it's done once _or_ with an identical target. However there's nothing to ensure (if done more than once) that it's being used to represent the same thing every time. That makes the code from  match methods like: > System.IObservable`1<TResult> System.Reactive.Linq.IQueryLanguage::Repeat(TResult) and > System.IObservable`1<TSource> System.Reactive.Linq.QueryLanguage::Repeat(System.IObservable`1<TSource>) where `TResult` is different in both checks. This patch tracks what is used as the generic parameter (on first check) and make sure it's identical if it's used again in the same signature. Note: this is a very old bug (i.e. it's always been that way) but recent changes to mono started to report such issues (a good thing) and, for AOT compilation on XI, that resulted in MT3001 errors.  https://github.com/mono/mono/blob/mono-3.10.0/mcs/tools/linker/Mono.Linker.Steps/TypeMapStep.cs#L250
…nnection. Fixes #31507
The socket would not be deleted with epoll_ctl (via epoll_reset_fd_at) when we would remove the state from threadpool_io.states. So when we would try to add it again, it would mark it as a new socket (as it wouldn't be present in threadpool_io.states), while it has not been deleted from epoll.
They are a very fragile part of the runtime, as they are not very well aken care of. We simply disable it by default for now. If everything still works as expected, we will completely remove the code.
…aces. Fixes #30904
…sing a destroyed mutex.
…ossible on osx
…. is passed an already gshared method.