Go to file
Kaveh R. Ghazi 03829ad289 c-typeck.c (convert_arguments): -Wtraditional now activates -Wconversion warnings...
* c-typeck.c (convert_arguments): -Wtraditional now activates
	-Wconversion warnings, except for changes in signed-ness.
	Detect complex<->int & int<->complex conversions as well.

	* invoke.texi (-Wtraditional): Document it.

testsuite:
	* gcc.dg/wtr-conversion-1.c: New testcase.

From-SVN: r41232
2001-04-10 22:40:48 +00:00
boehm-gc misc.c: Back out buggy changes to stack clearing code. 2001-04-06 17:11:43 -07:00
config
contrib
fastjar
gcc c-typeck.c (convert_arguments): -Wtraditional now activates -Wconversion warnings... 2001-04-10 22:40:48 +00:00
include
INSTALL
libchill
libf2c Daily bump. 2001-04-10 07:16:07 +00:00
libffi
libiberty
libjava testsuite: libjava: remove some xfail markers. 2001-04-10 14:27:41 +00:00
libobjc
libstdc++-v3 std_valarray.h (valarray<>::operator[]): Make inline. 2001-04-08 16:20:49 +00:00
maintainer-scripts
zlib
.cvsignore
ChangeLog * MAINTAINERS: Add self and RTH as C front end maintainers. 2001-04-06 18:14:46 +01:00
config-ml.in
config.guess
config.if
config.sub config.sub: Make sure to match an already-canonicalized machine name (eg. 2001-04-06 07:06:32 +00:00
configure
configure.in
COPYING
COPYING.LIB
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS * MAINTAINERS: Add self and RTH as C front end maintainers. 2001-04-06 18:14:46 +01:00
Makefile.in
missing
mkdep
mkinstalldirs
move-if-change
README
symlink-tree
ylwrap

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.


Check the INSTALL directory for detailed configuration and installation
instructions.


Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.