From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G7XfW-0004nf-Nk for qemu-devel@nongnu.org; Mon, 31 Jul 2006 09:18:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G7XfR-0004kV-Ra for qemu-devel@nongnu.org; Mon, 31 Jul 2006 09:18:50 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G7XfR-0004kQ-JM for qemu-devel@nongnu.org; Mon, 31 Jul 2006 09:18:45 -0400 Received: from [64.233.184.226] (helo=wr-out-0506.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G7Xi6-0002S6-Fl for qemu-devel@nongnu.org; Mon, 31 Jul 2006 09:21:30 -0400 Received: by wr-out-0506.google.com with SMTP id 71so276562wri for ; Mon, 31 Jul 2006 06:18:42 -0700 (PDT) Message-ID: <44CE032D.7050709@gmail.com> Date: Mon, 31 Jul 2006 15:18:37 +0200 MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Fix warnings in mips_r4k.c References: <44CDD962.7020900@gmail.com> <200607311339.37105.paul@codesourcery.com> In-Reply-To: <200607311339.37105.paul@codesourcery.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: Dirk Behme Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org Paul Brook wrote: > On Monday 31 July 2006 11:20, Dirk Behme wrote: > >>Fix warnings >> >>hw/mips_r4k.c: In function ‘mips_r4kc_init’: >>hw/mips_r4k.c:230: warning: pointer targets in passing >>argument 3 of ‘load_elf’ differ in signedness >>hw/mips_r4k.c:256: warning: pointer targets in passing >>argument 1 of ‘strcpy’ differ in signedness > > Compile with -Wno-pointer-sign. gcc4 isn't really supported anyway. Yes, I know ;) And yes, I know there are technical reasons for not supporting gcc4. But do you wan't to say that at places, where because of typos or lazy programming and thus no technical reason for it (e.g. passing signed where calling function wants unsigned) it is better to disable warning with -Wno-pointer-sign instead of fixing it? Note that I haven't fixed a lot of other similar warnings where there may be technical reasons for it. But in this file I thought its worth fixing and improving code quality. Regards Dirk