[Dropping linux-wireless, as there is nothing wireless below] On Thu, 2007-03-08 at 17:45 +0100, Johannes Berg wrote: > make CC="gcc -save-temps -D__CHECKER__" KBUILD_NOCMDDEP=1 M=drivers/net/wireless/mac80211/rt2x00/ > > and aborted when I got lots of errors, rt2400pci.i was created and has > about 26k lines. Running sparse on it (sparse rt2400pci.i) takes a lot > of memory too. I put the file up at > http://johannes.sipsolutions.net/files/rt2400pci.i Thanks! I see it now. Sparse is taking about 700M on x86 and 1100M on x86_64, which is much more than it uses for other files. Valgrind reports something interesting, but not necessarily related to the memory hogging: ==15775== Warning: invalid file descriptor -1 in syscall read() ==15775== Source and destination overlap in memcpy(0xBEFA84B4, 0xBEFA84D0, 48) ==15775== at 0x4007242: memcpy (mc_replace_strmem.c:402) ==15775== by 0x805E5CB: sort_list (sort.c:207) ==15775== by 0x8061D7C: cleanup_and_cse (cse.c:247) ==15775== by 0x805DE7B: linearize_symbol (linearize.c:2147) ==15775== by 0x804AEC2: check_symbols (sparse.c:266) ==15775== by 0x804B296: main (sparse.c:284) If sparse is compiled without optimization, the "overlap" warning is not reported. I think it can be ignored. It takes several minutes for sparse to process rt2400pci.i under valgrind. I haven't tried looking for leaks yet. Reducing the file may be tricky, since there is no definite way to say if the problem exists once the code becomes shorter. But I'll try. -- Regards, Pavel Roskin - To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
