public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: davem@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: target/6466: Sparc backend uses bad types for frame size calculation.
Date: Thu, 25 Apr 2002 19:36:00 -0000	[thread overview]
Message-ID: <20020426023554.6456.qmail@sources.redhat.com> (raw)


>Number:         6466
>Category:       target
>Synopsis:       Sparc backend uses bad types for frame size calculation.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 25 19:36:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     davem@redhat.com
>Release:        GCC 3.1 CVS
>Organization:
>Environment:
sparc-linux-gnu
>Description:
Lots of code in the sparc backend dealing with computing
the frame size uses 'int' where HOST_WIDE_INT is more
appropriate.  The attached testcase, when compiled for
any sparc target will show the errors that result,
such as "save" instructions with an immediate operand
being a very large negative number.
>How-To-Repeat:
Compile above program on Sparc, look at assembler
output or try to run the testcase :-)
>Fix:
Make Sparc backend use HOST_WIDE_INT as appropriate.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="bug.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bug.c"

dm9pZCBmb28gKGNoYXIgKnApCnsKICByZXR1cm47Cn0KCmludCBtYWluKHZvaWQpCnsKICBjaGFy
IHhbMHg3ZmZmZmZmMF07CiAgZm9vICh4KTsKCiAgZXhpdCAoMCk7Cn0K


             reply	other threads:[~2002-04-26  2:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25 19:36 davem [this message]
2002-04-25 19:37 davem
2003-05-17  9:56 target/6466: [SPARC] " Dara Hazeghi
2003-05-21  9:42 ehrhardt

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=20020426023554.6456.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).