[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-20 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 --- Comment #12 from Jakub Jelinek --- Author: jakub Date: Fri Dec 20 08:23:42 2019 New Revision: 279633 URL: https://gcc.gnu.org/viewcvs?rev=279633&root=gcc&view=rev Log: PR target/92841 * config/i386/i386.md (*stack_protect_set

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-17 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 --- Comment #11 from Jakub Jelinek --- Author: jakub Date: Tue Dec 17 20:40:01 2019 New Revision: 279468 URL: https://gcc.gnu.org/viewcvs?rev=279468&root=gcc&view=rev Log: PR target/92841 * config/i386/i386.md (@stack_protect_set

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-10 Thread bp at alien8 dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 --- Comment #10 from Boris --- Ok, fair enough. After all, security is not free. :) If you need me to test anything else, lemme know. Thx guys.

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-10 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 --- Comment #9 from Jakub Jelinek --- There is a scheduling pass in between the peephole2 which this patch uses and the final pass, so it is possible there was some other instruction in between before scheduling, thus the peephole2 didn't trigger

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-10 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 --- Comment #8 from Jakub Jelinek --- In the patch attached in this PR, yes, but I think it is fixed in the one I've posted to gcc-patches - https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00664.html

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-10 Thread bp at alien8 dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 --- Comment #7 from Boris --- Created attachment 47465 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47465&action=edit Micha's patterns fix Fix for mix-up between patterns with and without multi-nodes.

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-10 Thread bp at alien8 dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 --- Comment #6 from Boris --- Ok, so there was a mix-up between patterns with and without multi-nodes in your untested fix, which Micha found and fixed, see attached patch. (otherwise it wouldn't even build a whole kernel). With it, it fixed the

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-09 Thread bp at alien8 dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 --- Comment #5 from Boris --- Hohumm, looks good - this is the same site it generated with your patch: # arch/x86/kernel/cpu/scattered.c:48: { movq%gs:40, %rax# MEM[( long unsigned int *)40B], prephitmp_18 movq%rax, 1

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-09 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 Jakub Jelinek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned a

[Bug target/92841] Optimize -fstack-protector-strong code generation a bit

2019-12-09 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|