[Bug tree-optimization/91811] 256-bit vector store isn't used

rguenth at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Thu Sep 19 06:25:00 GMT 2019


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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-*-*
                 CC|                            |rguenth at gcc dot gnu.org
             Blocks|                            |53947

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
0x4ef6030 width_2(D) 1 times vec_construct costs 32 in prologue
0x4ef6030 width_2(D) 1 times vector_store costs 24 in body
0x4f59760 width_2(D) 1 times scalar_store costs 12 in body
0x4f59760 height_4(D) 1 times scalar_store costs 12 in body
0x4f59760 x_6(D) 1 times scalar_store costs 12 in body
0x4f59760 y_8(D) 1 times scalar_store costs 12 in body
t2.c:18:3: note:  Cost model analysis:
  Vector inside of basic block cost: 24
  Vector prologue cost: 32
  Vector epilogue cost: 0
  Scalar cost of basic block: 48
t2.c:18:3: missed:  not vectorized: vectorization is not profitable.
t2.c:18:3: note: ***** Re-trying analysis with vector size 16

so target costs say that this isnt profitable.  Probably a dup of one of the
bugs saying we don't take into account function boundary ABI for costing.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
[Bug 53947] [meta-bug] vectorizer missed-optimizations


More information about the Gcc-bugs mailing list