Overly-keen format string warning?

[Dave Korn]

  I added some debugging printfs, and ...

> cc1: warnings being treated as errors
> /gnu/gcc/gcc/gcc/dwarf2out.c: In function 'add_location_or_const_value_attribute
> ':
> /gnu/gcc/gcc/gcc/dwarf2out.c:13532:1: error: format '%p' expects type 'void *',
> but argument 3 has type 'struct var_loc_list *'
> /gnu/gcc/gcc/gcc/dwarf2out.c:13532:1: error: format '%p' expects type 'void *',
> but argument 4 has type 'struct var_loc_node *'
> /gnu/gcc/gcc/gcc/dwarf2out.c:13532:1: error: format '%p' expects type 'void *',
> but argument 5 has type 'rtx'
> /gnu/gcc/gcc/gcc/dwarf2out.c:13532:1: error: format '%p' expects type 'void *',
> but argument 3 has type 'struct var_loc_list *'
> /gnu/gcc/gcc/gcc/dwarf2out.c:13532:1: error: format '%p' expects type 'void *',
> but argument 4 has type 'struct var_loc_node *'
> /gnu/gcc/gcc/gcc/dwarf2out.c:13532:1: error: format '%p' expects type 'void *',
> but argument 5 has type 'rtx'
> make: *** [dwarf2out.o] Error 1
> 
> DKAdmin@ubik /gnu/gcc/obj.libstdc.enabled/gcc

  Should the format string warnings really be complaining about this on a
platform (i686-pc-cygwin) where there's only one kind of pointer?  I don't get
the rationale, if this is intentional.

    cheers,
      DaveK