https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121120
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|WAITING |RESOLVED
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Thomas de Bock from comment #3)
> Is it really? The problem I have with the codegen and the desired output
> from clang, in this example seems distinct enough from the problem bug
> 108953 reported to have with the assembly. Since they likely require
> different solutions (although possibly similar/related), is a separate bug
> report not justified?
PR 108953 is about the same missed optimization; the defaulted operator==
produces worse code generation for GCC compared to LLVM.
As I mentioned LLVM has a pass which cleans up the code to generate memcmp.
*** This bug has been marked as a duplicate of bug 108953 ***
