Re: Can shrink-wrapping ever move prologue past an ASM statement?

2015-07-08 Thread Josh Poimboeuf
On Wed, Jul 08, 2015 at 04:14:20PM -0500, Segher Boessenkool wrote: > On Wed, Jul 08, 2015 at 03:51:12PM -0500, Josh Poimboeuf wrote: > > > > > > For other archs, e.g. x86-64, you can do > > > > > > > > > > > > register void *sp asm(&

Re: Can shrink-wrapping ever move prologue past an ASM statement?

2015-07-08 Thread Josh Poimboeuf
On Wed, Jul 08, 2015 at 11:22:34AM -0500, Josh Poimboeuf wrote: > On Wed, Jul 08, 2015 at 05:36:31AM -0500, Segher Boessenkool wrote: > > On Wed, Jul 08, 2015 at 11:23:09AM +0200, Martin Jambor wrote: > > > > For other archs, e.g. x86-64, you can do > > > > >

Re: Can shrink-wrapping ever move prologue past an ASM statement?

2015-07-08 Thread Josh Poimboeuf
On Wed, Jul 08, 2015 at 11:37:35AM -0500, Segher Boessenkool wrote: > On Wed, Jul 08, 2015 at 11:22:34AM -0500, Josh Poimboeuf wrote: > > > Writing the asm with a clobber of the stack pointer causes all stack > > > accesses to go via the frame pointer, which causes prett

Re: Can shrink-wrapping ever move prologue past an ASM statement?

2015-07-08 Thread Josh Poimboeuf
On Wed, Jul 08, 2015 at 05:36:31AM -0500, Segher Boessenkool wrote: > On Wed, Jul 08, 2015 at 11:23:09AM +0200, Martin Jambor wrote: > > > For other archs, e.g. x86-64, you can do > > > > > > register void *sp asm("%sp"); > > > asm volatile("call func" : "+r"(sp)); > > > > > Well, I only ha