public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35368] [4.1/4.2/4.3/4.4 Regression] With #pragma visibility, `vtable for __cxxabiv1::__class_type_info' is emitted as a hidden-visibility relocation
Date: Mon, 25 Feb 2008 15:55:00 -0000 [thread overview]
Message-ID: <20080225155438.4001.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35368-11332@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from rguenth at gcc dot gnu dot org 2008-02-25 15:54 -------
Doens't work for me with 4.1.3 20080114, 4.2.3 or 4.3.0 20080219. Works with
4.0.4 20060904.
The bogus reference is here:
.LEFDE5:
.hidden DW.ref.__gxx_personality_v0
.weak DW.ref.__gxx_personality_v0
.section
.data.DW.ref.__gxx_personality_v0,"awG",@progbits,DW.ref.__gxx_personality_v0,comdat
.align 4
.type DW.ref.__gxx_personality_v0, @object
.size DW.ref.__gxx_personality_v0, 4
DW.ref.__gxx_personality_v0:
.long __gxx_personality_v0
.hidden _ZTVN10__cxxabiv117__class_type_infoE
.hidden _ZTI1A
.hidden _ZTV1A
Maybe related to PR19159, but that is for systems w/o weak support. This
is a regression on the 4.1/4.2 branches.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mmitchel at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |wrong-code
Known to fail|4.3.0 |4.1.3 4.2.3 4.3.0
Known to work|4.2.1 |4.0.4 4.2.1
Priority|P3 |P1
Last reconfirmed|0000-00-00 00:00:00 |2008-02-25 15:54:38
date| |
Summary|With #pragma visibility, |[4.1/4.2/4.3/4.4 Regression]
|`vtable for |With #pragma visibility,
|__cxxabiv1::__class_type_inf|`vtable for
|o' is emitted as a hidden- |__cxxabiv1::__class_type_inf
|visibility relocation |o' is emitted as a hidden-
| |visibility relocation
Target Milestone|--- |4.1.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35368
next prev parent reply other threads:[~2008-02-25 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 15:17 [Bug c++/35368] New: " benjamin at smedbergs dot us
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 ` rguenth at gcc dot gnu dot org [this message]
2008-02-25 16:19 ` [Bug c++/35368] [4.1/4.2/4.3/4.4 Regression] " 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=20080225155438.4001.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).