From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13619 invoked by alias); 23 Mar 2004 21:41:29 -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 13603 invoked from network); 23 Mar 2004 21:41:29 -0000 Received: from unknown (HELO Cantor.suse.de) (195.135.220.2) by sources.redhat.com with SMTP; 23 Mar 2004 21:41:29 -0000 Received: from hermes.suse.de (Hermes.suse.de [195.135.221.8]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by Cantor.suse.de (Postfix) with ESMTP id 53B1A355D0D; Tue, 23 Mar 2004 22:40:29 +0100 (CET) Message-ID: <4060AEFE.3060603@suse.de> Date: Wed, 24 Mar 2004 05:57:00 -0000 From: Paolo Carlini User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: Richard.Kreckel@ginac.de Cc: gcc@gcc.gnu.org Subject: Re: 128-bit long long? References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg01371.txt.bz2 Richard B. Kreckel wrote: >Hmmm, I've always believed that the next sentence ("However, if an >implementation provides integer types with widths of 8, 16, 32 or 64 bits, >it shall define the corresponding typedef names") is to be construed as a >*requirement* of these types on machines where they make sense. > I agree. Paolo.