From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14261 invoked by alias); 19 Oct 2002 03:43:25 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 14241 invoked from network); 19 Oct 2002 03:43:25 -0000 Received: from unknown (HELO gateway.sf.frob.com) (64.163.212.31) by sources.redhat.com with SMTP; 19 Oct 2002 03:43:25 -0000 Received: from magilla.sf.frob.com (magilla.sf.frob.com [198.49.250.228]) by gateway.sf.frob.com (Postfix) with ESMTP id 5FC22357E; Fri, 18 Oct 2002 20:43:24 -0700 (PDT) Received: (from roland@localhost) by magilla.sf.frob.com (8.11.6/8.11.6) id g9J3hNn02855; Fri, 18 Oct 2002 20:43:23 -0700 Date: Fri, 18 Oct 2002 20:55:00 -0000 Message-Id: <200210190343.g9J3hNn02855@magilla.sf.frob.com> From: Roland McGrath To: GNU libc hackers Subject: ia64 t_scalar_t definition X-shopping-list: (1) Satanic democratic bomb travesty (2) Inauspicious prosecutors (3) Audacious connotation expectations X-SW-Source: 2002-10/txt/msg00075.txt.bz2 t_scalar_t and t_uscalar_t are defined as 32 bits on ia64, while on other platforms they seem to be the word size. Is that really right? These types seem only to be used by some STREAMS structures that nothing in libc itself uses, so I don't know what if anything has ever actually used these types.