From: Josef Wolf <jw@raven.inka.de>
To: gcc-help@gcc.gnu.org
Subject: Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
Date: Fri, 18 Oct 2019 09:00:00 -0000 [thread overview]
Message-ID: <20191018085314.GE11171@raven.inka.de> (raw)
In-Reply-To: <d96df2bc-2c2a-fe19-183c-6a0893237888@arm.com>
Thanks for your help, Richard!
On Thu, Oct 17, 2019 at 03:55:31PM +0100, Richard Earnshaw (lists) wrote:
> On 17/10/2019 15:04, Josef Wolf wrote:
> >On Thu, Oct 17, 2019 at 02:37:11PM +0200, Matthias Pfaller wrote:
> >>Why is the stack pointer so low at this point of execution? Using
> >>0x20018000-0x20017d20 == 0x2e0 bytes of stack seems a little excessive
> >>for just one call.
> >
> >Ah!... Looks like you've spotted the problem! Actually, the SP is decremented
> >on every cycle of the loop:
> >
> > (gdb) disass
> > Dump of assembler code for function memset:
> > 0x08001008 <+0>: push {r4, lr}
> > 0x0800100a <+2>: mov r4, r0
> > 0x0800100c <+4>: cbz r2, 0x8001014 <memset+12>
> > => 0x0800100e <+6>: uxtb r1, r1
> > 0x08001010 <+8>: bl 0x8001008 <memset>
> > 0x08001014 <+12>: mov r0, r4
> > 0x08001016 <+14>: pop {r4, pc}
> > End of assembler dump.
> >
> >This looks REALLY suspicous to me. Every cycle of the loop in memset() is
> >pushing something onto the stack?!?
> >
> >Without the -ftree-loop-distribute-patterns option, the memset() function
> >looks entirely different:
> >
> > cbz r2, <memset+18>
> > add r2, r0
> > subs r2, #1
> > uxtb r1, r1
> > subs r3, r0, #1
> > <+10>: strb.w r1, [r3, #1]!
> > cmp r3, r2
> > bne.n <memset+10>
> > <+18>: bx lr
>
> The compiler has spotted that you've written something that acts like memset
> and optimized it into a function call to memset. So now you're recursing to
> oblivion. Try adding -fno-builtin-memset to your compile options.
This sounds reasonable, and I was actually thinking it would solve the
problem.
Unfortunately, -fno-built-memset doesn't have any effect. The same code is
generated.
--
Josef Wolf
jw@raven.inka.de
next prev parent reply other threads:[~2019-10-18 9:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 13:19 Josef Wolf
2019-10-16 13:30 ` Matthias Pfaller
2019-10-17 8:10 ` Josef Wolf
2019-10-16 18:18 ` Martin Sebor
2019-10-17 11:40 ` Josef Wolf
2019-10-17 12:37 ` Matthias Pfaller
2019-10-17 14:10 ` Josef Wolf
2019-10-17 14:55 ` Richard Earnshaw (lists)
2019-10-18 9:00 ` Josef Wolf [this message]
2019-10-18 10:26 ` Richard Earnshaw (lists)
2019-10-18 12:10 ` Josef Wolf
2019-10-18 13:07 ` Segher Boessenkool
2019-10-18 13:40 ` Josef Wolf
2019-10-18 12:50 ` Josef Wolf
2019-10-18 14:04 ` Richard Earnshaw (lists)
2019-10-18 9:10 ` Propagating addresses from linker to the runtie (was: Re: Crash when cross compiling for ARM with GCC-8-2-0 and) -ftree-loop-distribute-patterns Josef Wolf
2019-10-18 9:15 ` Propagating addresses from linker to the runtie Florian Weimer
2019-10-18 9:50 ` Josef Wolf
2019-10-18 10:47 ` Florian Weimer
2019-10-18 12:51 ` Segher Boessenkool
2019-10-18 12:56 ` Florian Weimer
2019-10-18 14:14 ` Segher Boessenkool
2019-10-18 14:34 ` Florian Weimer
2019-10-18 13:30 ` Josef Wolf
2019-10-18 14:20 ` Segher Boessenkool
2019-10-18 13:10 ` Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns Josef Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191018085314.GE11171@raven.inka.de \
--to=jw@raven.inka.de \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).