public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55023] hppa: wrong code generated with tail call optimisation
Date: Thu, 08 Jan 2015 21:30:00 -0000	[thread overview]
Message-ID: <bug-55023-4-KPjoK1OIlb@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 #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan  8 21:29:44 2015
New Revision: 219361

URL: https://gcc.gnu.org/viewcvs?rev=219361&root=gcc&view=rev
Log:
    PR target/55023
    PR middle-end/64388
    * dse.c (struct insn_info): Mention frame_read set also
    before reload for tail calls on some targets.
    (scan_insn): Revert 2014-12-22 change.  Set frame_read
    also before reload for tail calls if
    HARD_FRAME_POINTER_IS_ARG_POINTER.  Call add_wild_read
    instead of add_non_frame_wild_read for non-const/memset
    tail calls after reload.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/dse.c


      parent reply	other threads:[~2015-01-08 21:30 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
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 [this message]

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-KPjoK1OIlb@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).