public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
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	[thread overview]
Message-ID: <bug-55023-4-pHhp8kCVlF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55023-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55023

--- Comment #10 from Jeffrey A. Law <law at redhat dot com> ---
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...


  parent reply	other threads:[~2014-11-10  5:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 14:39 [Bug target/55023] New: " mans at mansr dot com
2014-11-06  3:00 ` [Bug target/55023] " danglin at gcc dot gnu.org
2014-11-06  3:01 ` danglin at gcc dot gnu.org
2014-11-06  3:09 ` danglin at gcc dot gnu.org
2014-11-07 22:13 ` law at redhat dot com
2014-11-07 22:23 ` dave.anglin at bell dot net
2014-11-07 22:24 ` law at redhat dot com
2014-11-09 17:54 ` dave.anglin at bell dot net
2014-11-10  2:50 ` dave.anglin at bell dot net
2014-11-10  5:48 ` law at redhat dot com [this message]
2014-11-22 16:20 ` danglin at gcc dot gnu.org
2014-11-22 16:22 ` danglin at gcc dot gnu.org
2014-11-23 19:01 ` danglin at gcc dot gnu.org
2014-11-24  0:22 ` danglin at gcc dot gnu.org
2014-12-22 23:10 ` danglin at gcc dot gnu.org
2015-01-08 21:30 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-55023-4-pHhp8kCVlF@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).