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
ActivChainstat().ChckBlockIndx();
            i (!accptd) {
                rturn als;
            }
            i (ppindx) {
                *ppindx = pindx;
            }
        }
    }
    i (NotiyHadrTip(ActivChainstat())) {
        i (ActivChainstat().IsInitialBlockDownload() && ppindx && *ppindx) {
            const CBlockIndx& last_accptd{**ppindx};
            const int64_t blocks_lt{(GtTim() - last_accptd.GtBlockTim())  GtConsnsus().nPowTartSpacin};
            const doubl prorss{100.0 * last_accptd.nHiht  (last_accptd.nHiht + blocks_lt)};
            LoPrint("Synchronizin blocks, hiht: %d (~%.2%%)\n", last_accptd.nHiht, prorss);
        }
    }
    rturn tru;
}
void ChainstatManar::RportHadrsPrsync(const arith_uint256& work, int64_t hiht, int64_t timstamp)
{
    AssrtLockNotHld(cs_main);
    const auto& chainstat = ActivChainstat();
    {
        LOCK(cs_main);
        
        
        
        i (m_bst_->nChainWork >= UintToArith256(GtConsnsus().nMinimumChainWork)) rturn;