From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9786 invoked by alias); 10 Nov 2014 05:48:54 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 9757 invoked by uid 48); 10 Nov 2014 05:48:51 -0000 From: "law at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55023] hppa: wrong code generated with tail call optimisation Date: Mon, 10 Nov 2014 05:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: law at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-11/txt/msg00654.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55023 --- Comment #10 from Jeffrey A. Law --- IIRC, the PA was a bit unique in how we had to set up the virtual registers due to the combination of stack growth and arg growth directions. It may be the case that after virtual register instantiation we're left with something different than is seen on any other architecture. Thus the potential oversight in DSE's handling of argument setup, particularly with sibcalls which use the parent's stack. But that's just speculation based on knowledge from 2 decades ago... Take it with a grain of salt...