From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22223 invoked by alias); 26 Sep 2005 19:41:33 -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 21938 invoked by uid 48); 26 Sep 2005 19:41:15 -0000 Date: Mon, 26 Sep 2005 19:41:00 -0000 Message-ID: <20050926194115.21937.qmail@sourceware.org> From: "pinskia at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050926192427.24068.dann@godzilla.ics.uci.edu> References: <20050926192427.24068.dann@godzilla.ics.uci.edu> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c/24068] Unconditional warning when using -combine X-Bugzilla-Reason: CC X-SW-Source: 2005-09/txt/msg03106.txt.bz2 List-Id: ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-26 19:41 ------- Because one file uses K&R style function defintions and the other uses a prototype which is ANSI/ISO style. Simple example: file1.c: int f(int); --- file2.c: int f(a) int a; { return a; } --- Compile it as: gcc file2.c file1.c -combine So this about the following: int f(a) int a; { return a; } int f(int); Which is questionable. So I don't think this is not an inappropriate warning. -------------------------------------------- As an aside, I wish people would stop using K&R style C already. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24068