[Bug target/84064] ICE in ix86_expand_prologue related to -fstack-clash-protection and memcpy on i686

2018-01-30 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84064 --- Comment #6 from Jeffrey A. Law --- WRT c#3, yea, that code is totally broken and probably has been since the day it was introduced. The good news is its fixable.

[Bug target/84064] ICE in ix86_expand_prologue related to -fstack-clash-protection and memcpy on i686

2018-01-30 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84064 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/84064] ICE in ix86_expand_prologue related to -fstack-clash-protection and memcpy on i686

2018-01-30 Thread law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84064 --- Comment #4 from Jeffrey A. Law --- Author: law Date: Wed Jan 31 05:02:30 2018 New Revision: 257217 URL: https://gcc.gnu.org/viewcvs?rev=257217=gcc=rev Log: PR target/84064 * i386.c (ix86_adjust_stack_and_probe_stack_clash):

[Bug target/84064] ICE in ix86_expand_prologue related to -fstack-clash-protection and memcpy on i686

2018-01-30 Thread fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84064 Florian Weimer changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug target/84064] ICE in ix86_expand_prologue related to -fstack-clash-protection and memcpy on i686

2018-01-26 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84064 --- Comment #2 from Jeffrey A. Law --- I wasn't ever happy with the discrepancy between the computation of TO_ALLOCATE in the layout code and ALLOCATE within ix86_expand_prologue. It seemed ripe to fall into this kind of problem. sigh. If

[Bug target/84064] ICE in ix86_expand_prologue related to -fstack-clash-protection and memcpy on i686

2018-01-26 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84064 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1