From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14000 invoked by alias); 10 Nov 2004 00:59:53 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 13943 invoked by uid 48); 10 Nov 2004 00:59:50 -0000 Date: Wed, 10 Nov 2004 00:59:00 -0000 Message-ID: <20041110005950.13942.qmail@sourceware.org> From: "manus at eiffel dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041109232340.18411.manus@eiffel.com> References: <20041109232340.18411.manus@eiffel.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c/18411] Warning not legitimate X-Bugzilla-Reason: CC X-SW-Source: 2004-11/txt/msg01196.txt.bz2 List-Id: ------- Additional Comments From manus at eiffel dot com 2004-11-10 00:59 ------- Ok, so why don't you generate the warning only when it makes sense. In my original case, I was passing a char and tell the C compiler it was a function pointer expecting a char. In this scenario it should not produce any warning. If you have incompatible types (such as int where you expect a float/double) then I'm ok that you generate a warning (although I would prefer an error since the generated code is incorrect). Or better, if possible, try to fix the inliner issue. Thanks, Manu -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18411