https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87288
Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-*-* i?86-*-* Status|UNCONFIRMED |NEW Keywords| |wrong-code Last reconfirmed| |2018-09-12 Component|tree-optimization |target CC| |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Known to fail| |9.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed on trunk. 0x0000000000400508 <+56>: movupd (%rax,%rdx,2),%xmm0 0x000000000040050d <+61>: movhpd 0x10(%rax,%rdx,2),%xmm0 => 0x0000000000400513 <+67>: movaps %xmm0,(%rsp,%rdx,1) 0x0000000000400517 <+71>: add $0x10,%rdx 0x000000000040051b <+75>: cmp %rdx,%rcx 0x000000000040051e <+78>: jne 0x400508 <main(int, char**)+56> and base_address: &jacobianTransposeds offset from base address: 0 constant offset from base address: 0 step: 8 base alignment: 16 base misalignment: 0 offset alignment: 128 step alignment: 8 base_object: MEM[(double &)&jacobianTransposeds] Access function 0: {0B, +, 8}_1 not sure where that offset 1 comes from... (also movaps vs. movapd, but ...).