On Tue, Aug 1, 2017 at 7:37 PM, Christopher Li <sparse@xxxxxxxxxxx> wrote:
> So you can't reproduce it. Let me dig deeper to see what is going on.
#0 pseudo_in_list (list=0x7f5a6972de10, pseudo=0x7f5a7aa65d68) at
liveness.c:163
#1 0x0000000000427924 in add_pseudo_exclusive (list=0x7f5a7dcf3758,
pseudo=0x7f5a7aa65d68)
at liveness.c:173
#2 0x0000000000427afe in track_bb_liveness (bb=0x7f5a7dcf3680) at
liveness.c:207
#3 0x0000000000427db9 in track_pseudo_liveness (ep=0x7f5a863d1010) at
liveness.c:250
#4 0x000000000041d313 in linearize_fn (sym=0x7f5a8c5fd8b0,
base_type=0x7f5a8c5fd990)
at linearize.c:2260
#5 0x000000000041d3b1 in linearize_symbol (sym=0x7f5a8c5fd8b0) at
linearize.c:2291
#6 0x0000000000401a08 in check_symbols (list=0x7f5a8c685910) at sparse.c:282
#7 0x0000000000401afe in main (argc=29, argv=0x7fff1f8d99c8) at sparse.c:303
I take a closer look, it seems sparse is spending a lot of time in
track_pseudo_liveness.
Compile with -O0 does not change any thing. At this point it could be
any thing.
Looking more into it.
Chris
--
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
