From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27687 invoked by alias); 31 May 2005 16:06:39 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27668 invoked by uid 22791); 31 May 2005 16:06:34 -0000 Received: from rwcrmhc13.comcast.net (HELO rwcrmhc13.comcast.net) (204.127.198.39) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 31 May 2005 16:06:34 +0000 Received: from [10.0.1.2] (c-24-61-199-96.hsd1.nh.comcast.net[24.61.199.96]) by comcast.net (rwcrmhc13) with SMTP id <2005053116063101500aj203e>; Tue, 31 May 2005 16:06:32 +0000 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Tue, 31 May 2005 20:45:00 -0000 Subject: Re: [RFC] solib-svr4.c gdb_byteised. From: Paul Schlie To: Manoj Iyer , "M.M. Kettenis" , Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-SW-Source: 2005-05/txt/msg00665.txt.bz2 > gcc4.0 complained abt the signedness... > > reversing gdb_byte to char for l_name_buf Unfortunately because GCC is schizophrenic. As although it has no problems assigning variables to each other which only differ in sign-ness (which may alter a value), it feels compelled warn about operations on pointers to such values (which are harmless). (arguably it seems that the best remedy would be to correct GCC, not attempt to appease it; as alternatively if all char's become gdb_byte, then might as well revert gdb_byte use, and simply compile with 'unsigned char'.)