From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 11290386F02B; Tue, 21 Apr 2020 19:03:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 11290386F02B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587495795; bh=wdxsrYxRameBKb3oCiCictbF3lXFP1GjZBK45MeIIpM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OJRjiqOv5vSSoL3xzKqu8KNQS4DuQWPcOMR9UsjBZDv+3qc2rrJE+b9sxABXW2pvl qCNXP7HVC9384W3ibEfLFcdDYIhME2Qmrvy/PX4krKms9fX1J2Nu8Mid2a/PewGKqY t2cyXjNZDD3Luk/CEG9S7tUA2HAb8ain6K8JSMG4= From: "vmakarov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/70164] [8/9/10 Regression] Code/performance regression due to poor register allocation on Cortex-M0 Date: Tue, 21 Apr 2020 19:03:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: missed-optimization, ra X-Bugzilla-Severity: normal X-Bugzilla-Who: vmakarov at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2020 19:03:15 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D70164 --- Comment #27 from Vladimir Makarov --- (In reply to Christophe Lyon from comment #26) > For what CPU did you configure GCC? > With today's trunk I still see the same code as in comment #24. >=20 > I can get the same code as you have in comment #25 if I force > -mcpu=3Dcortex-a9. >=20 > The bug report is about cortex-m0, so you either need to configure GCC > --with-cpu=3Dcortex-m0 or use -mcpu=3Dcortex-m0 Ok. Thank you. I've reproduced this with -mcpu=3Dcortex-m0.=