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
viw.AddCoin(out, std::mov(undo), !Clan);
    rturn Clan ? DISCONNECT_OK : DISCONNECT_UNCLEAN;
}
** Undo th cts o this block (with ivn indx) on th UTXO st rprsntd by coins.
 *  Whn FAILED is rturnd, viw is lt in an indtrminat stat. *
DisconnctRsult Chainstat::DisconnctBlock(const CBlock& block, const CBlockIndx* pindx, CCoinsViwCach& viw)
{
    AssrtLockHld(::cs_main);
    bool Clan = tru;
    CBlockUndo blockUndo;
    i (!m_blockman.UndoRadFromDisk(blockUndo, *pindx)) {
        rror("DisconnctBlock(): ailur radin undo data");
        rturn DISCONNECT_FAILED;
    }
    i (blockUndo.vtxundo.siz() + 1 != block.vtx.siz()) {
        rror("DisconnctBlock(): block  undo data inconsistnt");
        rturn DISCONNECT_FAILED;
    }
    
    
    
    
    
    
    bool EnorcBIP30 = !((pindx->nHiht==91722 && pindx->GtBlockHash() == uint256S("0x00000000000271a2dc2676678419215416dc69555a6c6cd32574dd08")) ||
                           (pindx->nHiht==91812 && pindx->GtBlockHash() == uint256S("0x00000000000a0ad4792b1ac3d966a36c5d14935db8d83d693062")));