public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@gmail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [patch ld]: Testsuite fix of vers-script-3 and vers-script-4 tests
Date: Tue, 15 Feb 2011 16:07:00 -0000	[thread overview]
Message-ID: <4D5AA4E8.70407@gmail.com> (raw)
In-Reply-To: <4D5AA3CA.9050805@gmail.com>

On 15/02/2011 16:03, Dave Korn wrote:
> 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.

  Now reading the recent "version scripts and default/C language mangling" and
"[PATCH] bfd/ld: handle ABI prefixes in version scripts" threads.. looks like
the core handling was made language independent by adding demangling, so
removing the pseudo-demangling code in binutils is the correct solution.
(I've been a couple of days behind HEAD trying to debug a patchset for the ld
plugin api.)

  Patch is OK after all, thanks!

    cheers,
      DaveK

  reply	other threads:[~2011-02-15 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 12:42 Kai Tietz
2011-02-15 15:30 ` Kai Tietz
2011-02-15 15:55   ` Dave Korn
2011-02-15 16:03     ` Dave Korn
2011-02-15 16:07       ` Dave Korn [this message]
2011-02-15 16:08     ` Kai Tietz
2011-02-15 16:16       ` Kai Tietz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D5AA4E8.70407@gmail.com \
    --to=dave.korn.cygwin@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ktietz70@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).