Pelles C forum

Pelles C => Bug reports => Topic started by: TbSE on November 01, 2010, 06:19:35 PM

Title: "fatal error: Internal error: spill_at_range()"
Post by: TbSE on November 01, 2010, 06:19:35 PM
I am using: Version 6.50.4 Release Candidate #2.

When I try to build the zlib dll, in the IDE, I get:
Code: [Select]
Building adler32.obj.
Building compress.obj.
Building crc32.obj.
Building deflate.obj.
Building gzclose.obj.
Building gzlib.obj.
Building gzread.obj.
Building gzwrite.obj.
Building infback.obj.
Building inffast.obj.
Building inflate.obj.
E:\src\zlib-1.2.5\inflate.c(1406): fatal error: Internal error: spill_at_range().
*** Error code: 1 ***
Done.

I've added a .zip file of a test project, with the inflate.c and the needed header files, that reproduces the error.

Tamir.
Title: Re: "fatal error: Internal error: spill_at_range()"
Post by: TimoVJL on November 01, 2010, 07:25:58 PM
And this with extracted code:
Code: [Select]
typedef struct {
    unsigned char op;
    unsigned char bits;
    unsigned short val;
} code;

typedef enum {
    CODES,
    LENS,
    DISTS
} codetype;

int inflate_table(codetype type, unsigned short *lens, unsigned codes, code * *table, unsigned *bits, unsigned short *work);

const char inflate_copyright[] =
   " inflate 1.2.5 Copyright 1995-2010 Mark Adler ";

int inflate_table(type, lens, codes, table, bits, work)
codetype type;
unsigned short *lens;
unsigned codes;
code * *table;
unsigned *bits;
unsigned short *work;
{
    return 0;
}
inftrees-1.c(25): error #2120: Redeclaration of 'inflate_table', previously declared at C:\code\PellesC\test_6.5\zlib_test\inftrees-1.c(13); expected 'int __cdecl function(codetype, unsigned short int *, unsigned int, code * *, unsigned int *, unsigned short int *)' but found 'int __cdecl function()'.
*** Error code: 1 ***
Title: Re: "fatal error: Internal error: spill_at_range()"
Post by: Pelle on November 04, 2010, 06:01:48 PM
I can reproduce it, maybe even fix it... we'll see...
Title: Re: "fatal error: Internal error: spill_at_range()"
Post by: TimoVJL on September 24, 2012, 02:34:57 PM
That redeclaration error still exists ?