From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32664 invoked by alias); 28 Jun 2005 16:38:18 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 32595 invoked by uid 22791); 28 Jun 2005 16:38:13 -0000 Received: from us01smtp2.synopsys.com (HELO kiruna.synopsys.com) (198.182.44.80) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 28 Jun 2005 16:38:13 +0000 Received: from mother.synopsys.com (mother.synopsys.com [146.225.100.171]) by kiruna.synopsys.com (Postfix) with ESMTP id 1D5EAF4E9; Tue, 28 Jun 2005 09:39:07 -0700 (PDT) Received: from piper.synopsys.com (localhost [127.0.0.1]) by mother.synopsys.com (8.9.1/8.9.1) with ESMTP id JAA25253; Tue, 28 Jun 2005 09:38:10 -0700 (PDT) Received: from piper.synopsys.com (localhost [127.0.0.1]) by piper.synopsys.com (8.12.10/8.12.3) with ESMTP id j5SGcAOe009612; Tue, 28 Jun 2005 09:38:10 -0700 Received: (from jbuck@localhost) by piper.synopsys.com (8.12.10/8.12.10/Submit) id j5SGcA5O009610; Tue, 28 Jun 2005 09:38:10 -0700 Date: Tue, 28 Jun 2005 16:38:00 -0000 From: Joe Buck To: Robert Dewar Cc: Gabriel Dos Reis , Andrew Pinski , gcc mailing list Subject: Re: signed is undefined and has been since 1992 (in GCC) Message-ID: <20050628163810.GC9524@synopsys.com> References: <6d9fa260f233e519762c7d11276a35ad@physics.uc.edu> <3dbad9a6bd7eb1aea74ff2245eaa1b99@physics.uc.edu> <42C115D5.8070503@adacore.com> <42C13D4D.9040604@adacore.com> <42C14930.40402@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42C14930.40402@adacore.com> User-Agent: Mutt/1.4.1i X-SW-Source: 2005-06/txt/msg01138.txt.bz2 On Tue, Jun 28, 2005 at 08:57:20AM -0400, Robert Dewar wrote: > Gabriel Dos Reis wrote: > = > >Please do remember that this is hardware dependent. If you have > >problems with x86, it does not mean you have the same witha PPC or a > >Sparc. > > But the whole idea of hardware semantics is bogus, since you are > assuming some connection between C and the hardware which does not > exist. C is not an assembly language. Actually, those of us who work in hardware-software codesign and formal verification consider exactly such problems, though it ends up being a comparison of the behavior of two abstract machines, the (idealized) processor model and the "C machine". The distinction between an HLL and assembly language is that in the latter, every program that is accepted by the tool is mapped into some definite machine language (though the processor architecture will flag the behavior of some instructions as undefined).