From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104861 invoked by alias); 17 Oct 2019 08:10:16 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 104706 invoked by uid 89); 17 Oct 2019 08:10:15 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=HX-Languages-Length:775 X-HELO: mail.inka.de Received: from quechua.inka.de (HELO mail.inka.de) (193.197.184.2) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 17 Oct 2019 08:10:14 +0000 Received: from raven.inka.de (uucp@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1iL0rL-00011H-LZ; Thu, 17 Oct 2019 10:10:11 +0200 Received: by raven.inka.de (Postfix, from userid 1000) id 7E670120164; Thu, 17 Oct 2019 10:02:28 +0200 (CEST) Date: Thu, 17 Oct 2019 08:10:00 -0000 From: Josef Wolf To: gcc-help@gcc.gnu.org Subject: Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns Message-ID: <20191017080228.GB11171@raven.inka.de> Mail-Followup-To: Josef Wolf , gcc-help@gcc.gnu.org References: <20191016131759.GA11171@raven.inka.de> <70a5c3f4-b448-e041-0202-3aa88a408914@marco.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <70a5c3f4-b448-e041-0202-3aa88a408914@marco.de> User-Agent: Mutt/1.5.24 (2015-08-30) X-IsSubscribed: yes X-SW-Source: 2019-10/txt/msg00062.txt.bz2 Thanks for your help, Matthias! On Wed, Oct 16, 2019 at 03:30:42PM +0200, Matthias Pfaller wrote: > > Is your stack part of the BSS? In that case the call to memset will > cause a crash. This would be an explanation. But the stack doesn't seem to be part of BSS: _sbss = 0x20003758 ;; Start of bss _ebss = 0x20012b48 ;; End of BSS _susrstack = 0x20012b48 ;; Start of user stack (not used in this application) _eusrstack = 0x20013b48 ;; End of user stack (not used in this application) SP = 0x20017d20 ;; Value of stack pointer when memset() is entered _estack = 0x20018000 ;; Initial stack pointer So I don't see anything that might be wrong here. -- Josef Wolf jw@raven.inka.de