virtex: passing argument 2 of 'ppc_exc_set_handler' from incompatible pointer type

[Ralf Corsepius]

The virtex BSP contains this:

libbsp/powerpc/virtex/irq/irq_init.c:int C_dispatch_irq_handler (CPU_Interrupt_frame *frame, unsigned int excNum)
libbsp/powerpc/virtex/irq/irq_init.c: ppc_exc_set_handler(ASM_EXT_VECTOR, C_dispatch_irq_handler);
libbsp/powerpc/virtex/irq/irq_init.c: ppc_exc_set_handler(ASM_BOOKE_DEC_VECTOR, C_dispatch_irq_handler);

i.e. it tries to install

int C_dispatch_irq_handler (CPU_Interrupt_frame *frame, unsigned int excNum)

via

ppc_exc_set_handler

(from libcpu/powerpc/new-exceptions/bspsupport/vectors.h)
which expects

int (*ppc_exc_handler_t)(BSP_Exception_frame *f, unsigned vector)

as second argument.

This manifests in gcc issuing these warnings:
./../../../../../../../c/src/lib/libbsp/powerpc/virtex/irq/irq_init.c:324:2: warning: passing argument 2 of 'ppc_exc_set_handler' from incompatible pointer type [enabled by default]
../../../../../../../../c/src/lib/libbsp/powerpc/virtex/irq/irq_init.c:325:2: warning: passing argument 2 of 'ppc_exc_set_handler' from incompatible pointer type [enabled by default]

No idea about how to fix this. Seems as if a change to the powerpc's exception handling wasn't propagated to the virtex BSP.

[Sebastian Huber]

Fixed on CVS head.

[Gedare Bloom]

Replace Version=HEAD with Version=4.11 for the tickets with Milestone >= 4.11