From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17860 invoked by alias); 5 Jul 2005 20:41:59 -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 17839 invoked by uid 22791); 5 Jul 2005 20:41:55 -0000 Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 05 Jul 2005 20:41:55 +0000 Received: from Relay1.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.suse.de (Postfix) with ESMTP id 247651C7BD; Tue, 5 Jul 2005 22:41:53 +0200 (CEST) Message-ID: <42CAF0C1.90106@suse.de> Date: Tue, 05 Jul 2005 20:41:00 -0000 From: Paolo Carlini User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 MIME-Version: 1.0 To: Michael Veksler Cc: gcc@gcc.gnu.org Subject: Re: tr1::unordered_set bizarre rounding behavior (x86) References: In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2005-07/txt/msg00197.txt.bz2 Michael Veksler wrote: >There is one more thing to consider: the ABI. >By changing the code in the header file will break the ABI >of tr1::unordered_set. Code compiled with older gcc and >newer and fixed-gcc will not interoperate. > > No, no, there are no problems. First, I don't see how changing the internals of a function like an hashing function would change the Binary Interface. Second, in general, we make no guarantees as far as the tr1 bits are concerned, this is also *explicitely* stated in the release notes. Really, please reconsider the issue, there are no problems. Paolo.