From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-93187-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 6943 invoked by alias); 21 Mar 2004 19:37:49 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 6936 invoked from network); 21 Mar 2004 19:37:48 -0000
Received: from unknown (HELO Cantor.suse.de) (195.135.220.2)
  by sources.redhat.com with SMTP; 21 Mar 2004 19:37:48 -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 786B333ACA1;
	Sun, 21 Mar 2004 20:37:48 +0100 (CET)
Message-ID: <405DEF3A.8050101@suse.de>
Date: Mon, 22 Mar 2004 00:12:00 -0000
From: Paolo Carlini <pcarlini@suse.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Scott Robert Ladd <coyote@coyotegulch.com>
Cc: Zack Weinberg <zack@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: 128-bit long long?
References: <405DB46B.80208@coyotegulch.com> <8765cykqws.fsf@egil.codesourcery.com> <405DEB4F.4020604@coyotegulch.com>
In-Reply-To: <405DEB4F.4020604@coyotegulch.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-03/txt/msg01268.txt.bz2

Scott Robert Ladd wrote:

> I always wondered why C99 didn't define both int128_t and uint128_t in 
> <stdint.h>.

However, according to 7.18.1.1, p3, intN_t and uintN_t are *all* optional.

I wonder if any 64 bit architecture actually provides 128bit integer types,
typedef-ed in stdint.h. Sparc64?!? s390x?!?

Paolo.