From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EE385386197C; Wed, 8 Jul 2020 17:01:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EE385386197C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1594227682; bh=Yku7qn0Fn0xDAaTf0l1DCdh7zHkOjj5DjIQ34r4cS5g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=pcQtLlIY8meDvVCxcWoOT7fbfZGuc9v2uwRD6mrV9HfBJ//sfLwW7sCAQTHL7X5Ln 7wkdF6BJfFLZ/6EcoEN2eVEjf7PZ+xEogul7vUa30sgS/K7gMqaVdg/6pJTnzbKrha NNixF+10xAn0YXExmPXJMxdF/ycSwReZN0obeF1o= From: "law at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/96015] [10/11 Regression] gcc-10.1.0 miscompiles Python on hppa Date: Wed, 08 Jul 2020 17:01:22 +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: 10.1.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: law at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.2 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: Wed, 08 Jul 2020 17:01:23 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96015 --- Comment #35 from Jeffrey A. Law --- That's a reasonable idea Eric -- the barriers are primarily there for the benefit of CFG building and manipulation and thus provide marginal, if any, benefit once we hit the reorg pass. I recall 81025 being particularly difficult to reproduce, but once understo= od it was pretty obvious what was going on. We could certainly look at your i= dea and see how it interacts with shrink-wrapping and the dwarf bits. I don't mind putting it on my todo list, but it's likely stage3 before I'd = be able to reasonably look at it.=