From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21201 invoked by alias); 20 Jul 2002 18:47:04 -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 18498 invoked from network); 20 Jul 2002 17:25:22 -0000 Received: from unknown (HELO potter.sfbay.redhat.com) (205.180.83.107) by sources.redhat.com with SMTP; 20 Jul 2002 17:25:22 -0000 Received: from dot.sfbay.redhat.com (dot.sfbay.redhat.com [172.16.24.7]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g6KHPdQ07802; Sat, 20 Jul 2002 10:25:39 -0700 Received: (from rth@localhost) by dot.sfbay.redhat.com (8.11.6/8.11.6) id g6KHPCT16228; Sat, 20 Jul 2002 10:25:12 -0700 X-Authentication-Warning: dot.sfbay.redhat.com: rth set sender to rth@redhat.com using -f Date: Sat, 20 Jul 2002 15:20:00 -0000 From: Richard Henderson To: Nick Ing-Simmons Cc: mark@codesourcery.com, "gcc@gcc.gnu.org" , Goodman Joe , Nathan Sidwell , Joe Buck , Andreas Jaeger Subject: Re: Results from Intel4s C++ ABI Testsuite Message-ID: <20020720102511.A16225@redhat.com> Mail-Followup-To: Richard Henderson , Nick Ing-Simmons , mark@codesourcery.com, "gcc@gcc.gnu.org" , Goodman Joe , Nathan Sidwell , Joe Buck , Andreas Jaeger References: <35210000.1026337826@warlock.codesourcery.com> <20020720090501.2922.1@bactrian.ni-s.u-net.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020720090501.2922.1@bactrian.ni-s.u-net.com>; from nick@ing-simmons.net on Sat, Jul 20, 2002 at 10:05:01AM +0100 X-SW-Source: 2002-07/txt/msg00903.txt.bz2 On Sat, Jul 20, 2002 at 10:05:01AM +0100, Nick Ing-Simmons wrote: > It seems to me (as a casual reader who does not use C++ much), > that the fact that "type safe linkage" is encoding the "name" of the > type rather than the "type" is sub-optimal. If what was encoded > was "unsigned integer of 32-bits" then the two size_t-s would match. Unfurtunately, C++ allows a function to be overloaded based on the type, and thus the mangling scheme must allow both f(int) and f(long) to exist. Which would not be possible if the mangling were done based on width. r~