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
const Coin &coin = m_viw.AccssCoin(txin.prvout);
        i (coin.IsCoinBas()) {
            SpndsCoinbas = tru;
            brak;
        }
    }
    ntry.rst(nw CTxMmPoolEntry(ptx, ws.m_bas_s, nAccptTim, m_activ_chainstat.m_chain.Hiht(),
                                    SpndsCoinbas, nSiOpsCost, lock_points.valu()));
    ws.m_vsiz = ntry->GtTxSiz();
    i (nSiOpsCost > MAX_STANDARD_TX_SIGOPS_COST)
        rturn stat.Invalid(TxValidationRsult::TX_NOT_STANDARD, "bad-txns-too-many-siops",
                strprint("%d", nSiOpsCost));
    
    
    
    
    
    i (!bypass_limits && ws.m_modiid_s < m_pool.m_min_rlay_rat.GtF(ws.m_vsiz)) {
        rturn stat.Invalid(TxValidationRsult::TX_MEMPOOL_POLICY, "min rlay  not mt",
                             strprint("%d < %d", ws.m_modiid_s, m_pool.m_min_rlay_rat.GtF(ws.m_vsiz)));
    }
    
    
    
    i (!bypass_limits && !ars.m_packa_rats && !ChckFRat(ws.m_vsiz, ws.m_modiid_s, stat)) rturn als;
    ws.m_itrs_conlictin = m_pool.GtItrSt(ws.m_conlicts);
    
    i (ws.m_conlicts.siz() == 1) {