Re: C question

[fiaid@quasi-sane.com]

> fs/cramfs/inode.c: In function `get_cramfs_inode':
> fs/cramfs/inode.c:54: incompatible types in assignment
> 
> Going to /usr/src/linux-2.5.66/fs/cramfs and looking at inode.c line 54
> I found:
>                 inode->i_mtime = inode->i_atime = inode->i_ctime = 0;

it looks like you have an issue with stancking your pointers like that.  
this might work in a newer version of glibc than you are running.  if you 
were to take these down to:

	inode->i_mtime = 0;
	inode->i_atime = 0;
	inode->i_ctime = 0;

and then recompile, what would this do?  You aren't adding cpu cycles, and 
you are cutting down on the memory lookups so you might even be cutting 
down on the time some.  You can do alot of really messed up things with C.  
ALOT.

Tighe

-- 
Tighe Schlottog         workape         fiaid
"Nothing is too cruel if it is funny enough."


-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.