public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Andrew D. Isaacson" <adisaacs@mtu.edu>
To: egcs@cygnus.com
Subject: bug, with testcase (alpha-unknown-linux-gnu)
Date: Fri, 05 Dec 1997 01:21:00 -0000	[thread overview]
Message-ID: <199712050757.CAA05343@wiley.sas.it.mtu.edu> (raw)

hello,

Mesa-2.3 fails to compile on linux-axp due to a compiler error in
triangle.c.  I've isolated the problem to this testcase, which gives
the following output from egcs-1.0:

trurl: gcc -c -O test.c
test.c: In function `lambda_textured_triangle':
test.c:25: internal error--unrecognizable insn:
(insn 206 203 207 (set (reg:DI 4 $4)
        (plus:DI (reg:DI 30 $30)
            (const_int 33680))) -1 (nil)
    (nil))
gcc: Internal compiler error: program cc1 got fatal signal 6

Oddly, if I delete any of the unused arrays from the testcase, the
problem fails to manifest.

Platform: alpha-unknown-linux-gnu (RedHat 5.0; glibc 2.0.5c), egcs 1.0

----test.c-----
float compute_lambda(float, float);
static void lambda_textured_triangle()
{   
    unsigned char flat_shade = 0;
    int a;
    int subTriangle;
    for (subTriangle=0; subTriangle<=1; subTriangle++) {
        int i, n = 5;
        unsigned short zspan[1600];
        unsigned char red[1600], green[1600];
        unsigned char alpha[1600];
        float s[1600 ], t[1600], u[1600];
        float   lambda [1600] ;
        if (flat_shade) {
            for (i=0;i<n;i++) {
                alpha[i] = a;
            }
        }
        else {
            for (i=0;i<n;i++) {
                lambda[i] = compute_lambda( s[i], t[i]);
            }
        }
    }
}
----end test.c-----

-andy
-- 
Andy Isaacson <adisaacs@mtu.edu> <adi@acm.org> / Linux/Alpha, C, Perl, Java
Fight Spam, join CAUCE: http://www.cauce.org  / Ultimate Frisbee, Footbag
http://www.csl.mtu.edu/~adisaacs/            / I speak for noone but myself

                 reply	other threads:[~1997-12-05  1:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199712050757.CAA05343@wiley.sas.it.mtu.edu \
    --to=adisaacs@mtu.edu \
    --cc=egcs@cygnus.com \
    /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).