From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-207298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28160 invoked by alias); 17 Jan 2007 00:47:30 -0000
Received: (qmail 28070 invoked by uid 48); 17 Jan 2007 00:47:17 -0000
Date: Wed, 17 Jan 2007 00:47:00 -0000
Message-ID: <20070117004717.28069.qmail@sourceware.org>
X-Bugzilla-Reason: CC
References: <bug-11856-781@http.gcc.gnu.org/bugzilla/>
Subject: [Bug c++/11856] unsigned warning in template
In-Reply-To: <bug-11856-781@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2007-01/txt/msg01318.txt.bz2



------- Comment #13 from manu at gcc dot gnu dot org  2007-01-17 00:47 -------
#include <cassert>
template <typename Int, Int D>
void f(Int x) {
  assert(0 <= x and x <= D);
}
int main() {
  f<unsigned char, 2>(5);
  f<signed char, 2>(5);
}


We don't emit a warning when instantiated as a signed char, so everything boils
down to having an option to disable the warning, doesn't it?

There is a patch pending review for that:
http://gcc.gnu.org/ml/gcc-patches/2007-01/msg01120.html


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11856