![]() | |||||||||||||
Messages in this thread |
* Rik van Riel <riel@redhat.com> wrote: > GCC 4 isn't very happy. Mostly sign changes, but also something that > looks like a real error: > > gcc -g -O3 -Wall -c -o fsck-cache.o fsck-cache.c > fsck-cache.c: In function 'main': > fsck-cache.c:59: warning: control may reach end of non-void function 'fsck_tree' being inlined > fsck-cache.c:62: warning: control may reach end of non-void function 'fsck_commit' being inlined > > I assume that fsck_tree and fsck_commit should complain loudly if they > ever get to that point - but since I'm not quite sure there's no > patch, sorry. i sent a patch for most of the sign errors, but the above is a case gcc not noticing that the function can never ever exit the loop, and thus cannot get to the 'return' point. Ingo - 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-04-10 19:42 [from the cache] ©2003-2008 | |||||||||||||