On Tue, Sep 15, 2009 at 05:20:06PM +0100, Dave Korn wrote: > > 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 > > > > dkad...@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.
Yes. It still is a type violation, even if it will work in most cases. Just for the record, before working on GCC, I wrote the front end of a C compiler for a machine (Data General MV/Eclipse) that had different types of pointers, and it was definately a hassle, particularly in the era before prototypes were added to the language. -- Michael Meissner, IBM 4 Technology Place Drive, MS 2203A, Westford, MA, 01886, USA meiss...@linux.vnet.ibm.com
