https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107014
--- Comment #7 from Alexander Monakov <amonakov at gcc dot gnu.org> --- I wanted to understand what gets exposed in LTO mode that causes a blowup. I'd say flatten is not appropriate for this function (I don't think you want to force inlining of memset or _find_next_bit?), so might be better to go back to the original issue and solve the problem in a more focused way (e.g. force-inlining the function which needs to access __initdata if you really need the verification that triggers otherwise).
