public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: davem@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: target/6496: Sparc backend clobbers call-return stack of UltraSparc
Date: Sat, 27 Apr 2002 23:46:00 -0000	[thread overview]
Message-ID: <20020428064357.4555.qmail@sources.redhat.com> (raw)


>Number:         6496
>Category:       target
>Synopsis:       Sparc backend clobbers call-return stack of UltraSparc
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 27 23:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     davem@redhat.com
>Release:        GCC 3.1 CVS
>Organization:
>Environment:
sparc*-*
>Description:
The Sparc backend peepholes for optimizing a
call followed by a jump should be disabled when
optimizing for UltraSPARC and later.

These optimizations corrupt the call-return stack
so that the end result is slower code not faster code.
>How-To-Repeat:
Compile enclosed testcase with -O2 -mtune=ultrasparc
Look at assembly for "add %o7, OFF, %o7" in delay
slot of calls to 'bar'.
>Fix:
When sparc_pu == PROCESSOR_ULTRASPARC or later, do not
match these peepholes.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="call_jump.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="call_jump.c"

ZXh0ZXJuIHZvaWQgYmFyKHZvaWQpOwoKaW50IGZvbyhpbnQgYSkKewoJaWYgKGEgPj0gMCAmJiBh
IDwgOCkKCXsKCQlhICs9IDB4NTAwMDA7CgkJYmFyKCk7Cgl9CgllbHNlIGlmIChhIDwgMTgpCgl7
CgkJYSArPSAweDgyMDAzMDsKCQliYXIoKTsKCX0KCWVsc2UgaWYgKGEgPiAzMikKCQlhICs9IDB4
OTkyMjg4MzsKCWVsc2UKCQliYXIoKTsKCglyZXR1cm4gYTsKfQo=


             reply	other threads:[~2002-04-28  6:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-27 23:46 davem [this message]
2002-04-28 22:38 davem

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=20020428064357.4555.qmail@sources.redhat.com \
    --to=davem@redhat.com \
    --cc=gcc-gnats@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).