On 11/02/14 16:00, Bram Moolenaar wrote:
Patch 7.4.174
Problem: Compiler warnings for Python interface. (Tony Mechelynck)
Solution: Add type casts, initialize variable.
Files: src/if_py_both.h
In incremental build for patches 173-175 I get the following:
- In tiny build but not in huge build:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -O2
-fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
-o objects/move.o move.c
move.c: In function ‘scroll_cursor_halfway’:
move.c:2104:14: warning: unused variable ‘old_topline’ [-Wunused-variable]
- In huge build (tiny build has no Python):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14
-pthread -DORBIT2=1 -D_REENTRANT -I/usr/include/libgnomeui-2.0
-I/usr/include/libart-2.0 -I/usr/include/gconf/2
-I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0
-I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0
-I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/gnome-vfs-2.0 -I/usr/lib64/gnome-vfs-2.0/include
-I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
-I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0
-I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2
-I/usr/include/pango-1.0 -I/usr/include/gail-1.0
-I/usr/include/freetype2 -I/usr/include/atk-1.0
-I/usr/lib64/gtk-2.0/include -I/usr/include/cairo
-I/usr/include/pixman-1 -I/usr/include/libpng14 -O2
-fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
-I/usr/include -D_LARGEFILE64_SOURCE=1 -I/usr/include/python2.7
-DPYTHON_HOME='"/usr"' -pthread -fPIE -o objects/if_python.o if_python.c
In file included from if_python.c:809:0:
if_py_both.h: In function ‘_DictionaryItem’:
if_py_both.h:1620:2: warning: dereferencing type-punned pointer will
break strict-aliasing rules [-Wstrict-aliasing]
Best regards,
Tony.
--
Use at own risk.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
