https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121405

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |13.5
      Known to fail|                            |5.1.0
            Summary|Another missed VN via a     |[13/14/15/16 Regression]
                   |copy (but via an int copy)  |Another missed VN via a
                   |                            |copy (but via an int copy)
           Severity|enhancement                 |normal
      Known to work|                            |4.9.4

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So when memcpy->using an integer type started to happen, the optimization
started to be missed.

If the vectorizer creates a CONSTRUCTOR here, then GCC is able to optimize it
(either -fno-vect-cost-model or on aarch64).

Reply via email to