From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elmo.sgh.dk (elmo.sgh.dk [139.59.133.142]) by sourceware.org (Postfix) with ESMTPS id BDE18383D802 for ; Sat, 19 Feb 2022 17:11:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BDE18383D802 Received: from [192.168.0.120] (5E8A5A6A.rev.sefiber.dk [94.138.90.106]) by elmo.sgh.dk (Postfix) with ESMTPSA id DA3411F8036 for ; Sat, 19 Feb 2022 17:11:29 +0000 (UTC) Message-ID: <9ec86f65-50dd-6780-936e-a849598911e1@sgh.dk> Date: Sat, 19 Feb 2022 18:11:26 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Content-Language: da To: gcc@gcc.gnu.org From: =?UTF-8?Q?S=c3=b8ren_Holm?= Subject: Bisected failure Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2022 17:11:34 -0000 Hi My application running on a stm32f7 started to behave "random" when compiled with gcc 10.1 - Gcc 9.x works fine. By random I mean this. 1. Flash the application onto the target. 2. reset - the application starts up fine 2. reset again - the application somehow goes haywire during startup effectively starting over with out a reset. That ends up leaving interrups and timers enabled fireing during BSS clear. 3. Reset again - now the application starts up fine again. 4. reset again - lockup again 5. reset again - lockup again 6 ....... I have bisected and verified that whatever makes my commit 79f1d8521882de51480866fd7037199d670316bd (HEAD, refs/bisect/bad) Author: Jan Hubicka Date: Thu Nov 14 14:30:46 2019 +0100 * params.opt (max-inline-insns-single-O2): Set to 70 (instead of 30). From-SVN: r278221 Do you have any ideas to how to hunt down this bug? Besides trying to isolate the place where things go wrong. I'm unsure if GCC does something that the hardware does not like or my application is buggy. In any case I'd like to figure out the root cause. I do not like to be stuck at gcc 9 because of these kinds of issues :) I'd appreciate any input you might have. /Søren