lkml.org 
[lkml]   [2001]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.4.9: GCC 3.0 problem in "acct.c"
Date
Alan Cox wrote:
> peter k. wrote:
>> i just updated my gcc from 2.96 to 3.0.1 and now i cant compile kernel 2.4.9
>> anymore, make bzImage fails with the following error message:
>>
>> acct.c: In function `check_free_space':
>> acct.c:147: Unrecognizable insn:
>> (insn 335 102 336 (parallel[
>> (set (reg/v:SI 2 ecx [44])
>> (const_int 0 [0x0]))
>> (clobber (reg:CC 17 flags))
>> ] ) -1 (insn_list:REG_DEP_ANTI 100 (insn_list:REG_DEP_ANTI 102
>> (nil)))
>> (expr_list:REG_UNUSED (reg:CC 17 flags)
>> (nil)))
>> acct.c:147: Internal compiler error in insn_default_length, at
>> insn-attrtab.c:223
>>
>> can anyone tell me how to fix this?
>
> Use gcc 2.96 or gcc 3.0.0. You broke the compiler. Please also see the gcc bug
> reporting instructions. You will actually make a gcc hacker very happy
> reporting that problem.

Except that a similar problem with capi existed allready with gcc 3.0 +
kernels 2.4.*, and that problem was reported to gcc people multiple
times. But it is still broken in gcc 3.0.1:

bp2.c:414: warning: `sbp2_host_info_lock' defined but not used
capi.c: In function `capi_ioctl':
capi.c:1031: Unrecognizable insn:
(insn/i 1675 3103 3100 (parallel[ capi.c:1031: Internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

So, does anyone have any ideas? That problem is critical because
it makes ISDN (capi 2) unusable with kernels 2.4.* + gcc 3.0.*

All other things seem to function pretty well with 2.4.9 + 3.0.1.

--
Mr. Santeri Kannisto, CTO, sk@sot.com - http://www.sot.com/
Ou SOT Finnish Software Engineering - fax +372 5 171 941
Kreutzwaldi 7-4, EE-10124 Tallinn - tel. +372 5 044 941
ESTONIA - http://bestlinux.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:58    [W:0.089 / U:0.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site