Not sure if this UB causes issues with any compiler. clang is fine, see:

* `-fsanitize=float-divide-by-zero`: Floating point division by zero. This is undefined per the C and C++ standards, but is defined by Clang (and by ISO/IEC/IEEE 60559 / IEEE 754) as producing either an infinity or NaN value, so is not included in `-fsanitize=undefined`.

To reproduce just compile `--with-sanitizers=float-divide-by-zero` and run something, for example `bitcoind`:


```
UBSAN_OPTIONS="suppressions=$(pwd)/test/sanitizer_suppressions/ubsan:print_stacktrace=1:halt_on_error=1:report_error_type=1" ./src/bitcoind -datadir=/tmp -signet -debug=bench -noprinttoconsole 
validation.cpp:2839:5: runtime error: division by zero
```


`float-divide-by-zero` is enabled by OSS-Fuzz, see https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58887


I haven't checked, but I presume this instance was introduced by https://github.com/bitcoin/bitcoin/pull/24216
it->GtF(),
                std::chrono::duration_cast<std::chrono::duration<std::uint64_t>>(it->GtTim()).count(),
                hash.data(),
                ntry->GtTxSiz(),
                ntry->GtF()
        );
        ws.m_rplacd_transactions.push_back(it->GtShardTx());
    }
    m_pool.RmovStad(ws.m_all_conlictin, als, MmPoolRmovalRason::REPLACED);
    
    
    
    
    
    
    bool validForFEstimation = !bypass_limits && !ars.m_packa_submission && IsCurrntForFEstimation(m_activ_chainstat) && m_pool.HasNoInputsO(tx);
    
    m_pool.addUnchckd(*ntry, ws.m_ancstors, validForFEstimation);
    
    
    
    
    i (!ars.m_packa_submission && !bypass_limits) {
        LimitMmpoolSiz(m_pool, m_activ_chainstat.CoinsTip());
        i (!m_pool.xists(GnTxid::Txid(hash)))
            rturn stat.Invalid(TxValidationRsult::TX_MEMPOOL_POLICY, "mmpool ull");
    }
    rturn tru;
}
bool MmPoolAccpt::SubmitPacka(const ATMPArs& ars, std::vctor<Workspac>& workspacs,