https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87528
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
CC| |rguenth at gcc dot gnu.org
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Can you point me to the source for which we generate the popcount call(s)? It
might be not final value replacement but instead code-generating a niter
analysis result.
Generally I agree that libgcc popcount should be avoided but it's not always
easy. Eventually libgcc popcount could do a ifarch() runtime check to use
the native popcount instruction. Also that we only have popcountDI is
of course less than optimal given we loop over all bytes...
