From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32447 invoked by alias); 15 Feb 2011 16:03:10 -0000 Received: (qmail 32434 invoked by uid 22791); 15 Feb 2011 16:03:09 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ww0-f43.google.com (HELO mail-ww0-f43.google.com) (74.125.82.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Feb 2011 16:03:04 +0000 Received: by wwi17 with SMTP id 17so308848wwi.12 for ; Tue, 15 Feb 2011 08:03:01 -0800 (PST) Received: by 10.227.157.201 with SMTP id c9mr3801111wbx.216.1297785781753; Tue, 15 Feb 2011 08:03:01 -0800 (PST) Received: from [192.168.2.99] (cpc2-cmbg8-0-0-cust61.5-4.cable.virginmedia.com [82.6.108.62]) by mx.google.com with ESMTPS id f27sm2883964wbf.13.2011.02.15.08.02.59 (version=SSLv3 cipher=OTHER); Tue, 15 Feb 2011 08:03:00 -0800 (PST) Message-ID: <4D5AA3CA.9050805@gmail.com> Date: Tue, 15 Feb 2011 16:03:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Kai Tietz CC: Binutils Subject: Re: [patch ld]: Testsuite fix of vers-script-3 and vers-script-4 tests References: <4D5AA1FB.2040905@gmail.com> In-Reply-To: <4D5AA1FB.2040905@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00167.txt.bz2 On 15/02/2011 15:55, Dave Korn wrote: > Nope. This causes two regressions on i686-pc-cygwin: > >> FAIL: vers-script-3 >> FAIL: vers-script-4 > > They pass currently. They fail with your patch. Ah, hang on: I just updated my sandbox, and I have found a suspect change: > 2011-02-14 Mike Frysinger <... > > * ldlang.c (lang_vers_match): Declare a new c_sym, assign it to > the bfd_demangle of sym, change users of sym to c_sym when not > already demangling, and free when done. Change callers of > cplus_demangle to bfd_demangle. This is likely to have changed the behaviour I guess. cheers, DaveK