From owner-freebsd-current Wed May 15 20:46:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id A756837B403; Wed, 15 May 2002 20:46:09 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 0EC3F4CECC; Wed, 15 May 2002 23:46:09 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id XAA12409; Wed, 15 May 2002 23:46:07 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id UAA27116; Wed, 15 May 2002 20:46:07 -0700 (PDT) Message-Id: <200205160346.UAA27116@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: rivers@dignus.com Subject: Re: moused(8): char signed-ness problem with gcc 3.1 Cc: audit@FreeBSD.ORG, knu@iDaemons.org, current@FreeBSD.ORG Date: Wed, 15 May 2002 20:46:06 -0700 Versions: dmail (solaris) 2.4/makemail 2.9b Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > So - yes - it seems gcc 3.1 does have a problem... Indeed - easily determined by breaking down the expression. So, who's gonna report it to gcc-bugs? knu?... int main() { unsigned char i = 127; char j; printf("%d\n", ((char)(i << 1))); j = ((char)(i << 1)) / 2; printf("%d\n", j); j = ((char)(i << 1)); printf("%d\n", j / 2); return 0; } Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message