On Tue, Aug 1, 2017 at 11:09 PM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Tue, Aug 1, 2017 at 4:33 PM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: >> >> When I try the command you gave with -rc4 sparse I get: >> real 0m3.281s >> user 0m3.175s >> sys 0m0.097s >> wich is very far from the 23-30s you got. Dunno what the difference could be. > > Did you run it with all the parameter? I did > If I just run the sort version: > > time sparse -m64 -c -o usp10.o usp10.c -I. -I../../../include > -D__WINESRC__ -D_REENTRANT > > It is: > real 0m4.532s > user 0m4.436s > sys 0m0.075s > > But if I run with all parameter. > > sh -x slow.sh > > + sparse -m64 -c -o usp10.o usp10.c -I. -I../../../include > -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing > -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers > -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits > -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith > -Wlogical-op -gdwarf-2 -gstrict-dwarf -g -O2 > /usr/include/sys/sysmacros.h:79:1: warning: constant > 0xfffff00000000000u is so big it is unsigned long > /usr/include/sys/sysmacros.h:80:1: warning: constant > 0x00000ffffff00000u is so big it is unsigned long > ... > > real 0m24.771s > user 0m24.447s > sys 0m0.213s > > Again, I haven't dig very deep with this yet. Might be a bug some where indeed. Here, both give essentially the same time. Which is quite normal as none of the 'additional' options should make any difference in how sparse is processing things: it's just some more flags for warnings and none of -fPIC -pipe -fno-strict-aliasing -gdwarf-2 -gstrict-dwarf -g has any effects for sparse and the only effect of -O2 is to define __OPTIMIZE__. -- Luc -- 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
