fs/ufs/inode.c:817: warning: array subscript is above array bounds

2007-01-31 Thread d binderman
Hello there, I just tried to compile Linux kernel 2.6.19.2 with the new GNU C compiler version 4.3 snapshot 20070126. The compiler said fs/ufs/inode.c:817: warning: array subscript is above array bounds The source code is for (i = 0; i < (UFS_NDADDR + UFS_NINDIR); i++)

fs/ufs/inode.c:817: warning: array subscript is above array bounds

2007-01-31 Thread d binderman
Hello there, I just tried to compile Linux kernel 2.6.19.2 with the new GNU C compiler version 4.3 snapshot 20070126. The compiler said fs/ufs/inode.c:817: warning: array subscript is above array bounds The source code is for (i = 0; i (UFS_NDADDR + UFS_NINDIR); i++)

fs/9p/vfs_inode.c(406): remark #593: variable "sb" was set but never used

2006-11-29 Thread d binderman
Hello there, I just tried to compile Linux kernel 2.6.18.3 with the Intel C C compiler. The compiler said 1. fs/9p/vfs_inode.c(406): remark #593: variable "sb" was set but never used The source code is struct super_block *sb = NULL; I have checked the source code and I agree with the

fs/9p/mux.c(786): remark #593: variable "cb" was set but never used

2006-11-29 Thread d binderman
Hello there, I just tried to compile Linux kernel 2.6.18.3 with the Intel C C compiler. The compiler said fs/9p/mux.c(786): remark #593: variable "cb" was set but never used The source code is v9fs_mux_req_callback cb; I have checked the source code and I agree with the compiler.

fs/9p/mux.c(786): remark #593: variable cb was set but never used

2006-11-29 Thread d binderman
Hello there, I just tried to compile Linux kernel 2.6.18.3 with the Intel C C compiler. The compiler said fs/9p/mux.c(786): remark #593: variable cb was set but never used The source code is v9fs_mux_req_callback cb; I have checked the source code and I agree with the compiler. Suggest

fs/9p/vfs_inode.c(406): remark #593: variable sb was set but never used

2006-11-29 Thread d binderman
Hello there, I just tried to compile Linux kernel 2.6.18.3 with the Intel C C compiler. The compiler said 1. fs/9p/vfs_inode.c(406): remark #593: variable sb was set but never used The source code is struct super_block *sb = NULL; I have checked the source code and I agree with the

mm/fremap.c(104): remark #593: variable "pte_val" was set but never used

2006-11-27 Thread d binderman
Hello there, I just tried to compile Linux kernel 2.6.18.3 with the Intel C C compiler. The compiler said mm/fremap.c(104): remark #593: variable "pte_val" was set but never used The source code is pte_t pte_val; I have checked the source code and I agree with the compiler. Suggest

mm/fremap.c(104): remark #593: variable pte_val was set but never used

2006-11-27 Thread d binderman
Hello there, I just tried to compile Linux kernel 2.6.18.3 with the Intel C C compiler. The compiler said mm/fremap.c(104): remark #593: variable pte_val was set but never used The source code is pte_t pte_val; I have checked the source code and I agree with the compiler. Suggest delete

file kernel/signal.c, 2 * array subscript out of range

2005-07-30 Thread d binderman
Hello there, I just tried to compile Redhat Fedora package kernel-2.6.12-1.1435_FC5 with the Intel C compiler version 8.1 The compiler said kernel/signal.c(196): warning #175: subscript out of range The source code is case 4: ready = signal->sig[3] &~ blocked->sig[3]; Clearly broken

file kernel/signal.c, 2 * array subscript out of range

2005-07-30 Thread d binderman
Hello there, I just tried to compile Redhat Fedora package kernel-2.6.12-1.1435_FC5 with the Intel C compiler version 8.1 The compiler said kernel/signal.c(196): warning #175: subscript out of range The source code is case 4: ready = signal-sig[3] ~ blocked-sig[3]; Clearly broken