Hello, The __PIC__ and __pic__ macros are now set in generic code and there is no need to fiddle with them in platform configuration. The change below removes the following warnings: <built-in>:0:0: warning: "__PIC__" redefined <built-in>:0:0: note: this is the location of the previous definition <built-in>:0:0: warning: "__pic__" redefined <built-in>:0:0: note: this is the location of the previous definition that were missed when porting the original change from an older version of GCC. Verified with `gcc -E -dD' built for --target=vax-linux to ensure correct behaviour. The configuration is not capable enough for regression testing yet. 2009-10-29 Maciej W. Rozycki <macro@linux-mips.org> * config/vax/linux.h (TARGET_OS_CPP_BUILTINS): Don't define __pic__ or __PIC__. OK to apply? Maciej gcc-4.5.0-20091029-vax-linux-pic.patch Index: gcc-4.5.0-20091029-vax-linux/gcc/config/vax/linux.h =================================================================== --- gcc-4.5.0-20091029-vax-linux.orig/gcc/config/vax/linux.h +++ gcc-4.5.0-20091029-vax-linux/gcc/config/vax/linux.h @@ -21,17 +21,7 @@ along with GCC; see the file COPYING3. #undef TARGET_VERSION #define TARGET_VERSION fprintf (stderr, " (VAX GNU/Linux with ELF)"); -#define TARGET_OS_CPP_BUILTINS() \ - do \ - { \ - LINUX_TARGET_OS_CPP_BUILTINS(); \ - if (flag_pic) \ - { \ - builtin_define ("__PIC__"); \ - builtin_define ("__pic__"); \ - } \ - } \ - while (0) +#define TARGET_OS_CPP_BUILTINS() LINUX_TARGET_OS_CPP_BUILTINS() /* We use GAS, G-float double and want new DI patterns. */ #undef TARGET_DEFAULT _______________________________________________ Linux-Vax mailing list Linux-Vax@mail.pergamentum.com http://mail.pergamentum.com/mailman/listinfo/linux-vax