Could one of you send a patch that fixes these compiler warnings? I made a few attempts at it but wasn't sure if changing the usb buffer to be a char * was appropriate, etc.

gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../src/helper - I../../src/target -gstabs+ -I/opt/local/include -MT rlink.o -MD - MP -MF .deps/rlink.Tpo -c -o rlink.o `test -f 'rlink/rlink.c' || echo './'`rlink/rlink.c
rlink/rlink.c: In function ‘ep1_generic_commandl’:
rlink/rlink.c:137: warning: pointer targets in passing argument 3 of ‘usb_bulk_write’ differ in signedness
rlink/rlink.c: In function ‘ep1_memory_write’:
rlink/rlink.c:254: warning: pointer targets in passing argument 3 of ‘usb_bulk_write’ differ in signedness
rlink/rlink.c: In function ‘dtc_load_from_buffer’:
rlink/rlink.c:362: warning: pointer targets in passing argument 2 of ‘strncmp’ differ in signedness
rlink/rlink.c: In function ‘dtc_start_download’:
rlink/rlink.c:454: warning: pointer targets in passing argument 3 of ‘usb_bulk_read’ differ in signedness rlink/rlink.c:481: warning: pointer targets in passing argument 3 of ‘usb_bulk_read’ differ in signedness
rlink/rlink.c: In function ‘dtc_run_download’:
rlink/rlink.c:507: warning: pointer targets in passing argument 3 of ‘usb_bulk_write’ differ in signedness rlink/rlink.c:528: warning: pointer targets in passing argument 3 of ‘usb_bulk_read’ differ in signedness rlink/rlink.c:549: warning: pointer targets in passing argument 3 of ‘usb_bulk_read’ differ in signedness
rlink/rlink.c: In function ‘rlink_init’:
rlink/rlink.c:1667: warning: pointer targets in passing argument 3 of ‘usb_bulk_read’ differ in signedness rlink/rlink.c:1706: warning: pointer targets in passing argument 3 of ‘usb_bulk_read’ differ in signedness rlink/rlink.c:1731: warning: pointer targets in passing argument 3 of ‘usb_bulk_read’ differ in signedness

--
Rick Altherr
[email protected]

"He said he hadn't had a byte in three days. I had a short, so I split it with him."
 -- Unsigned



Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to