public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "benjamin at smedbergs dot us" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35368] New: With #pragma visibility, `vtable for __cxxabiv1::__class_type_info' is emitted as a hidden-visibility relocation
Date: Mon, 25 Feb 2008 15:17:00 -0000 [thread overview]
Message-ID: <bug-35368-11332@http.gcc.gnu.org/bugzilla/> (raw)
Testcase attached: when a class is declared with #pragma visibility hidden on,
references to `vtable for __cxxabiv1::__class_type_info' are emitted with
relocations that assume hidden visibility. This is incorrect, and is a
regression against 4.1 and I think 4.2.
To reproduce, compile the testcase, on an ELF toolchain, with:
g++-4.3 -shared -frtti -fPIC -o libtest.so test-cpp-rtti-linkage-error.cpp
--
Summary: With #pragma visibility, `vtable for
__cxxabiv1::__class_type_info' is emitted as a hidden-
visibility relocation
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: benjamin at smedbergs dot us
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35368
next reply other threads:[~2008-02-25 15:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 15:17 benjamin at smedbergs dot us [this message]
2008-02-25 15:17 ` [Bug c++/35368] " benjamin at smedbergs dot us
2008-02-25 15:34 ` benjamin at smedbergs dot us
2008-02-25 15:55 ` [Bug c++/35368] [4.1/4.2/4.3/4.4 Regression] " rguenth at gcc dot gnu dot org
2008-02-25 16:19 ` matz at gcc dot gnu dot org
2008-02-26 16:31 ` jakub at gcc dot gnu dot org
2008-02-26 17:06 ` mmitchel at gcc dot gnu dot org
2008-02-26 17:19 ` jakub at gcc dot gnu dot org
2008-02-26 17:25 ` benjamin at smedbergs dot us
2008-02-26 17:39 ` jakub at gcc dot gnu dot org
2008-02-26 17:58 ` mark at codesourcery dot com
2008-02-27 9:10 ` jakub at gcc dot gnu dot org
2008-02-27 9:27 ` jakub at gcc dot gnu dot org
2008-02-27 9:32 ` [Bug c++/35368] [4.3/4.4 " jakub at gcc dot gnu dot org
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=bug-35368-11332@http.gcc.gnu.org/bugzilla/ \
--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).