Re: target/6466: Sparc backend uses bad types for frame size calculation.

Re: target/6466: Sparc backend uses bad types for frame size calculation.

[davem]

Synopsis: Sparc backend uses bad types for frame size calculation.

Responsible-Changed-From-To: unassigned->jakub
Responsible-Changed-By: davem
Responsible-Changed-When: Thu Apr 25 19:36:59 2002
Responsible-Changed-Why:
    Jakub already has a half-completed patch to deal
    with this problem post-3.1

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6466

Re: target/6466: [SPARC] backend uses bad types for frame size calculation.

[ehrhardt]

Synopsis: [SPARC] backend uses bad types for frame size calculation.

State-Changed-From-To: open->feedback
State-Changed-By: cae
State-Changed-When: Wed May 21 09:42:44 2003
State-Changed-Why:
    .

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6466

Re: target/6466: [SPARC] backend uses bad types for frame size calculation.

[Dara Hazeghi]

The following reply was made to PR target/6466; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: jakub@gcc.gnu.org, gcc-gnats@gcc.gnu.org, davem@redhat.com
Cc:  
Subject: Re: target/6466: [SPARC] backend uses bad types for frame size calculation.
Date: Sat, 17 May 2003 02:51:45 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=6466
 
 Hello,
 
 the report for this PR indicates that a patch was partly written in the  
 pre-3.1 era. Has there been any progress since? Is this bug still  
 present in current gcc versions? Thanks,
 
 Dara
 

target/6466: Sparc backend uses bad types for frame size calculation.

[davem]

>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