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

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

2011/2/15 Kai Tietz <ktietz70@googlemail.com>:
> Hello,
>
> ChangeLog
>
> 2011-02-15  Kai Tietz
>
>        * ld-pe/vers-script-3.ver: Add _Z* to global and use
>        wildcard for personality symbols.
>        * ld-pe/vers-script-4.ver: Likewise.
>
> Tested for x86_64-w64-mingw32 and i686-w64-mingw32. Ok for apply?
>
> Regards,
> Kai
>

Ok, I withdraw recent patch. It is just fixing the symptoms but not
the underlying issue.
For 32-bit COFF the real issue is in pe-dll.c file in function
process_def_file_and_drectve. Here the underscore of a symbol is
stripped, and the same time it is done in bfd_demangle, which is used
by bfd_find_version_for_sym. By this in 32-bit case with leading
underscores, they were stripped twice.

ChangeLog

2011-02-15  Kai Tietz

          * pe-dll.c (process_def_file_and_drectve): Don't strip
          leading underscore from symbol by calling bfd_find_version_for_sym.

Tested for x86_64-w64-mingw32, i686-pc-cygwin, and i686-w64-mingw32.
Ok for apply?

Regards,
Kai

[-- Attachment #2: pe_dll.txt --]
[-- Type: text/plain, Size: 622 bytes --]

Index: pe-dll.c
===================================================================
RCS file: /cvs/src/src/ld/pe-dll.c,v
retrieving revision 1.133
diff -u -3 -r1.133 pe-dll.c
--- pe-dll.c	27 Jun 2010 04:07:54 -0000	1.133
+++ pe-dll.c	15 Feb 2011 15:23:17 -0000
@@ -720,9 +720,8 @@
 	      if (lang_elf_version_info && would_export)
 		{
 		  bfd_boolean hide = 0;
-		  char ofs = pe_details->underscored && symbols[j]->name[0] == '_';
 		  (void) bfd_find_version_for_sym (lang_elf_version_info,
-				symbols[j]->name + ofs, &hide);
+				symbols[j]->name, &hide);
 		  would_export = !hide;
 		}
 	      if (would_export)

  reply	other threads:[~2011-02-15 15:30 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 [this message]
2011-02-15 15:55   ` Dave Korn
2011-02-15 16:03     ` Dave Korn
2011-02-15 16:07       ` Dave Korn
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=AANLkTiniZrpC_tLppYqvKUynjjZXNSspb62fFmUg7NnS@mail.gmail.com \
    --to=ktietz70@googlemail.com \
    --cc=binutils@sourceware.org \
    --cc=dave.korn.cygwin@gmail.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).