[Bug middle-end/109326] Bad assembler code generation for valid C on 886-64

2023-03-28 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109326 --- Comment #4 from Andrew Pinski --- (In reply to Steve Thompson from comment #3) > However I don't understand why olock_reset_op() is so large. It's > a trivial initializer for a descriptor with an array of olock_op_element > structures appen

[Bug middle-end/109326] Bad assembler code generation for valid C on 886-64

2023-03-28 Thread susurrus.of.qualia at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109326 --- Comment #3 from Steve Thompson --- (In reply to Andrew Pinski from comment #1) > init_olock_op_element_struct asm output looks fine to me: > > movzwl .LC0(%rip), %eax > movq$0, (%rdi) > movq$0, 8(%rdi) >

[Bug middle-end/109326] Bad assembler code generation for valid C on 886-64

2023-03-28 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109326 --- Comment #2 from Andrew Pinski --- Note if you are disassemblying the object file with objdump -d, you might want to add the -r option to enable dumping of the relocations that are produced too. In the init_olock_op_struct case you miss the r

[Bug middle-end/109326] Bad assembler code generation for valid C on 886-64

2023-03-28 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109326 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED