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/10567] -fno-delayed-branch not honored in back-end
Date: Wed, 07 Jul 2004 21:33:00 -0000	[thread overview]
Message-ID: <20040707213313.29568.qmail@sourceware.org> (raw)
In-Reply-To: <20030430161600.10567.davem@redhat.com>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-07-07 21:33 -------
Subject: Bug 10567

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	ebotcazou@gcc.gnu.org	2004-07-07 21:33:09

Modified files:
	gcc            : ChangeLog 
	gcc/config/sparc: sparc.c sparc.md 

Log message:
	PR target/10567
	* config/sparc/sparc.c (load_pic_register): Honor flag_delayed_branch.
	(output_return): Likewise.
	(output_sibcall): Abort if !flag_delayed_branch.
	(sparc_function_ok_for_sibcall): Return 0 if !flag_delayed_branch.
	(emit_and_preserve): New function.
	(sparc_output_mi_thunk): Use it.  Honor flag_delayed_branch.  Emit an
	indirect jump to the thunked-to function if !flag_delayed_branch.
	* config/sparc/sparc.md (delayed_branch): New attribute.
	(load_pcrel_sym): Honor flag_delayed_branch.  Use above
	attribute to compute the length of the insn.
	(goto_handler_and_restore): Likewise.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.4349&r2=2.4350
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/sparc/sparc.c.diff?cvsroot=gcc&r1=1.311&r2=1.312
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/sparc/sparc.md.diff?cvsroot=gcc&r1=1.206&r2=1.207



-- 


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


  parent reply	other threads:[~2004-07-07 21:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030430161600.10567.davem@redhat.com>
2003-05-26  8:53 ` [Bug target/10567] -fno-delayed-branch no honored when -mflat dhazeghi@yahoo.com
2003-05-26 14:11 ` pinskia@physics.uc.edu
2003-08-24  2:35 ` pinskia at gcc dot gnu dot org
2003-08-24  2:41 ` pinskia at gcc dot gnu dot org
2003-08-24  2:54 ` pinskia at gcc dot gnu dot org
2003-09-08  9:07 ` [Bug target/10567] -fno-delayed-branch not honored in function epilogues ebotcazou at gcc dot gnu dot org
2003-09-08  9:08 ` ebotcazou at gcc dot gnu dot org
2003-09-09 14:19 ` [Bug target/10567] -fno-delayed-branch not honored in back-end ebotcazou at gcc dot gnu dot org
2003-09-18 14:30 ` ebotcazou at gcc dot gnu dot org
2003-11-26  7:48 ` ebotcazou at gcc dot gnu dot org
2003-11-26  8:37 ` davem at gcc dot gnu dot org
2003-11-26  8:47 ` ebotcazou at gcc dot gnu dot org
2004-02-26  1:45 ` pinskia at gcc dot gnu dot org
2004-05-26 22:54 ` pinskia at gcc dot gnu dot org
2004-07-03  8:57 ` ebotcazou at gcc dot gnu dot org
2004-07-06 20:55 ` davem at gcc dot gnu dot org
2004-07-07 21:33 ` cvs-commit at gcc dot gnu dot org [this message]
2004-07-07 22:21 ` pinskia at gcc dot gnu dot org
2004-07-07 22:37 ` ebotcazou at gcc dot gnu dot org
2004-07-08  6:25 ` ebotcazou at gcc dot gnu dot org
2004-07-08  6:26 ` ebotcazou at gcc dot gnu dot org
2004-07-08 15:25 ` cvs-commit at gcc dot gnu dot 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=20040707213313.29568.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).