public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23774] dealloc of dynamic stack space breaks backchain
Date: Tue, 13 Sep 2005 03:02:00 -0000	[thread overview]
Message-ID: <20050913030158.14074.qmail@sourceware.org> (raw)
In-Reply-To: <20050908005521.23774.amodra@bigpond.net.au>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-09-13 03:01 -------
Subject: Bug 23774

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-4_0-branch
Changes by:	amodra@gcc.gnu.org	2005-09-13 03:01:08

Modified files:
	gcc            : ChangeLog 
	gcc/config/rs6000: rs6000.md 

Log message:
	PR target/23774
	* config/rs6000/rs6000.md (restore_stack_block): Write the backchain
	word before changing the stack pointer.	 Use gen_frame_mem for MEMs.
	Use UNSPEC_TIE to prevent insn scheduling reordering the insns.
	(restore_stack_nonlocal): Likewise.
	(save_stack_nonlocal): Use template to emit insns, and gen_frame_mem.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=2.7592.2.427&r2=2.7592.2.428
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/rs6000/rs6000.md.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.350.2.3&r2=1.350.2.4



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23774


  parent reply	other threads:[~2005-09-13  3:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08  0:55 [Bug target/23774] New: " amodra at bigpond dot net dot au
2005-09-08  0:57 ` [Bug target/23774] " amodra at bigpond dot net dot au
2005-09-08  3:22 ` amodra at bigpond dot net dot au
2005-09-09  3:14 ` pinskia at gcc dot gnu dot org
2005-09-13  0:33 ` amodra at bigpond dot net dot au
2005-09-13  2:01 ` cvs-commit at gcc dot gnu dot org
2005-09-13  3:02 ` cvs-commit at gcc dot gnu dot org [this message]
2005-09-13  4:07 ` amodra at bigpond dot net dot au

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=20050913030158.14074.qmail@sourceware.org \
    --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).