This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Patch to stop setting -Wno-error on varasm.o

I tested for varasm.c warnings in all cross-configurations.  AFAICT,
only one warning remains and it happens only when configuring for
c4x-unknown-rtems, but since -Werror is only active in stage2 (or
later) and I believe c4x is a cross-only target, it shouldn't matter.

Also bootstrapped C-only on sparc-sun-solaris2.7 and verified that we
no longer get -Wno-error on varasm.o in stage2 and later.

Ok for mainline?


2003-06-04  Kaveh R. Ghazi  <>

	* (varasm.o): Don't set -Wno-error.
diff -rup orig/egcc-CVS20030604/gcc/ egcc-CVS20030604/gcc/
--- orig/egcc-CVS20030604/gcc/	2003-06-04 04:35:32.000000000 -0400
+++ egcc-CVS20030604/gcc/	2003-06-04 17:01:12.030186808 -0400
@@ -158,7 +158,6 @@ GCC_WARN_CFLAGS = $(LOOSE_WARN) $($(@D)-
 # These files are to have -Werror bypassed in stage2:
 # These are very hard to completely clean due to target complexities.
-varasm.o-warn = -Wno-error
 gcc.o-warn = -Wno-error
 insn-conditions.o-warn = -Wno-error
 # Bison-1.75 output often yields (harmless) -Wtraditional warnings

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]