public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: zack@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: c/10604
Date: Sat, 03 May 2003 21:46:00 -0000	[thread overview]
Message-ID: <20030503214600.31137.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/10604; it has been noted by GNATS.

From: zack@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: c/10604
Date: 3 May 2003 21:44:31 -0000

 CVSROOT:	/cvs/gcc
 Module name:	gcc
 Changes by:	zack@gcc.gnu.org	2003-05-03 21:44:31
 
 Modified files:
 	gcc            : ChangeLog Makefile.in c-common.c c-opts.c 
 	                 c-typeck.c function.c stmt.c toplev.c 
 	gcc/cp         : ChangeLog typeck.c 
 	gcc/testsuite  : ChangeLog 
 Added files:
 	gcc/testsuite/g++.dg/warn: compare1.C 
 	gcc/testsuite/gcc.dg: compare7.c 
 
 Log message:
 	PR c/10604
 	
 	* c-common.c (warn_sign_compare): Initialize to -1.
 	* c-opts.c (c_common_init_options): Don't set warn_sign_compare here.
 	(c_common_decode_option <OPT_Wall>): Set warn_sign_compare
 	for C++ only.
 	(c_common_post_options): Set warn_sign_compare from extra_warnings
 	if it's still -1 at this point.
 	
 	* toplev.c (maybe_warn_unused_parameter): New static variable.
 	(set_Wextra): New static function.
 	(W_options): Remove "extra".
 	(decode_W_option): Call set_Wextra.
 	(independent_decode_option): Likewise.
 	(set_Wunused): Cooperate with set_Wextra in setting
 	warn_unused_parameter.
 	(rest_of_compilation): No need to check extra_warnings as
 	well as warn_uninitialized.
 	
 	* c-typeck.c (build_binary_op, build_conditional_expr):
 	No need to check extra_warnings as well as warn_sign_compare.
 	(internal_build_compound_expr): No need to check extra_warnings
 	as well as warn_unused_value.
 	* function.c (expand_function_end): No need to check extra_warnings
 	as well as warn_unused_parameter.
 	* stmt.c (expand_expr_stmt_value): No need to check extra_warnings
 	as well as warn_unused_value.
 	* cp/typeck.c (build_x_compound_expr): No need to check
 	extra_warnings as well as warn_unused_value.
 	
 	* doc/invoke.texi: Clarify documentation of -Wsign-compare.
 	* gcc.dg/compare7.c, g++.dg/warn/compare1.C: New testcases.
 	
 	* Makefile.in: Disable -Werror for gengtype-lex.o.
 
 Patches:
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=1.17678&r2=1.17679
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/Makefile.in.diff?cvsroot=gcc&r1=1.1046&r2=1.1047
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-common.c.diff?cvsroot=gcc&r1=1.413&r2=1.414
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-opts.c.diff?cvsroot=gcc&r1=1.41&r2=1.42
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-typeck.c.diff?cvsroot=gcc&r1=1.235&r2=1.236
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/function.c.diff?cvsroot=gcc&r1=1.423&r2=1.424
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/stmt.c.diff?cvsroot=gcc&r1=1.299&r2=1.300
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/toplev.c.diff?cvsroot=gcc&r1=1.750&r2=1.751
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.diff?cvsroot=gcc&r1=1.3361&r2=1.3362
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/typeck.c.diff?cvsroot=gcc&r1=1.457&r2=1.458
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.2646&r2=1.2647
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/warn/compare1.C.diff?cvsroot=gcc&r1=1.1&r2=1.2
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gcc.dg/compare7.c.diff?cvsroot=gcc&r1=1.1&r2=1.2
 


             reply	other threads:[~2003-05-03 21:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03 21:46 zack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-03  0:26 c/10604 zack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030503214600.31137.qmail@sources.redhat.com \
    --to=zack@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).