public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] fix -Wsign-compare error in objc-act.c (PR objc/50743)
Date: Sun, 16 Oct 2011 13:13:00 -0000	[thread overview]
Message-ID: <20122.49140.381473.924718@pilspetsen.it.uu.se> (raw)

This fixes a bootstrap failure on trunk with objc enabled, caused by a
recent change which introduced for-loops that compare a size_t index
variable with a TREE_VEC_LENGTH limit.  TREE_VEC_LENGTH returns a signed
integer, resulting in a signed/unsigned comparison.  The C++ front-end
fails to catch this error due to PR50012, but the C front-end correctly
catches it, breaking --disable-build-poststage1-with-cxx bootstraps.

Fixed by casting TREE_VEC_LENGTH to size_t before the comparisons.

Nicola Pero said the patch looked good, but also said he couldn't formally
approve it.

Ok for trunk?

(I don't have svn write access so I'll need someone else to commit it if
it's approved.)

/Mikael

gcc/objc/

2011-10-16  Mikael Pettersson  <mikpe@it.uu.se>

	PR objc/50743
	* objc-act.c (check_duplicates): Cast TREE_VEC_LENGTH result
	to size_t to avoid signed/unsigned comparison.
	(insert_method_into_method_map): Likewise.

--- gcc-4.7-20111015/gcc/objc/objc-act.c.~1~	2011-10-14 12:19:01.000000000 +0200
+++ gcc-4.7-20111015/gcc/objc/objc-act.c	2011-10-16 11:53:56.000000000 +0200
@@ -5070,7 +5070,7 @@ check_duplicates (tree method, int metho
      alignment.  */
   if (!warn_strict_selector_match)
     {
-      for (i = 0; i < TREE_VEC_LENGTH (method); i++)
+      for (i = 0; i < (size_t) TREE_VEC_LENGTH (method); i++)
 	if (!comp_proto_with_proto (first_method, TREE_VEC_ELT (method, i), 0))
 	  goto issue_warning;
       
@@ -5103,7 +5103,7 @@ check_duplicates (tree method, int metho
 	      identifier_to_locale (gen_method_decl (first_method)));
     }
   
-  for (i = 0; i < TREE_VEC_LENGTH (method); i++)
+  for (i = 0; i < (size_t) TREE_VEC_LENGTH (method); i++)
     {
       bool type = TREE_CODE (TREE_VEC_ELT (method, i)) == INSTANCE_METHOD_DECL;
       
@@ -5825,7 +5825,7 @@ insert_method_into_method_map (bool clas
 	  /* Check all the existing prototypes.  If any matches the
 	     one we need to add, there is nothing to do because it's
 	     already there.  */
-	  for (i = 0; i < TREE_VEC_LENGTH (existing_entry); i++)
+	  for (i = 0; i < (size_t) TREE_VEC_LENGTH (existing_entry); i++)
 	    if (comp_proto_with_proto (method, TREE_VEC_ELT (existing_entry, i), 1))
 	      return;
 
@@ -5837,7 +5837,7 @@ insert_method_into_method_map (bool clas
 	  new_entry = make_tree_vec (TREE_VEC_LENGTH (existing_entry) + 1);
 	  
 	  /* Copy the methods from the existing vector.  */
-	  for (i = 0; i < TREE_VEC_LENGTH (existing_entry); i++)
+	  for (i = 0; i < (size_t) TREE_VEC_LENGTH (existing_entry); i++)
 	    TREE_VEC_ELT (new_entry, i) = TREE_VEC_ELT (existing_entry, i);
 	  
 	  /* Add the new method at the end.  */

             reply	other threads:[~2011-10-16 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-16 13:13 Mikael Pettersson [this message]
2011-10-17  6:23 ` Mike Stump
2011-10-17  9:57 ` Nicola Pero
2011-10-17 23:01   ` Mikael Pettersson
2011-10-18 12:19     ` Nicola Pero

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=20122.49140.381473.924718@pilspetsen.it.uu.se \
    --to=mikpe@it.uu.se \
    --cc=gcc-patches@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).