public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave dot korn dot cygwin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39578] Linkage broken for dllimport vtables
Date: Sun, 29 Mar 2009 17:47:00 -0000	[thread overview]
Message-ID: <20090329174708.22109.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39578-14702@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from dave dot korn dot cygwin at gmail dot com  2009-03-29 17:47 -------
For Cygwin, we just recently made --enable-auto-import the default in CVS
binutils.  Now that we're moving to shared library runtimes throughout it made
sense.

However, I think this is a real bug, as it doesn't happen on 4.3.2; we get a
direct undefined reference to the import symbol in the object file:

$ g++ -g -o vttest.exe vttest.cpp libvttest.dll.a --save-temps

admin@ubik /tmp/vttest
$ nm vttest.o
00000000 b .bss
00000000 d .data
00000000 N .debug_abbrev
00000000 N .debug_aranges
00000000 N .debug_frame
00000000 N .debug_info
00000000 N .debug_line
00000000 N .debug_loc
00000000 N .debug_pubnames
00000000 N .debug_ranges
00000000 N .debug_str
00000000 d .eh_frame
00000000 t .text
00000000 t .text$_ZN10TestObjectC1Ev
00000000 T __ZN10TestObjectC1Ev
         U ___gxx_personality_v0
         U ___main
         U __imp___ZN10TestObject8VirtFuncEv
         U __imp___ZTV10TestObject
00000000 T _main

admin@ubik /tmp/vttest
$ 

My earlier build of 4.3.3 with the patch for PR36654 reverted does the same
thing.  However, as soon as I reapplied the patch and rebuilt cc1plus, I got
this output:

/tmp/vttest $ nm vttest.o    libvtt
00000000 b .bss
00000000 d .data
00000000 N .debug_abbrev
00000000 N .debug_aranges
00000000 N .debug_frame
00000000 N .debug_info
00000000 N .debug_line
00000000 N .debug_loc
00000000 N .debug_pubnames
00000000 N .debug_ranges
00000000 N .debug_str
00000000 d .eh_frame
00000000 t .text
00000000 t .text$_ZN10TestObjectC1Ev
00000000 T __ZN10TestObjectC1Ev
         U __ZTV10TestObject
         U ___gxx_personality_v0
         U ___main
         U __imp___ZN10TestObject8VirtFuncEv
00000000 T _main
/tmp/vttest $

So I think that confirms it.


-- 

dave dot korn dot cygwin at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dave dot korn dot cygwin at
                   |                            |gmail dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39578


  reply	other threads:[~2009-03-29 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29 15:28 [Bug target/39578] New: " tdragon at tdragon dot net
2009-03-29 17:47 ` dave dot korn dot cygwin at gmail dot com [this message]
2009-04-16 20:34 ` [Bug target/39578] " pinskia at gcc dot gnu dot org
2009-09-12  9:54 ` ktietz at gcc dot gnu dot org
     [not found] <bug-39578-4@http.gcc.gnu.org/bugzilla/>
2013-12-17 20:09 ` ktietz at gcc dot gnu.org
2013-12-18  0:50 ` tdragon at tdragon dot net

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=20090329174708.22109.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).