From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: KDE 3.4 visibility support disabled
Date: Thu, 26 May 2005 01:57:56 +0200 [thread overview]
Message-ID: <200505260157.56648@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <pan.2005.05.25.23.37.29.83224@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
[just to make sure that everybody will hear that]
On Thursday 26 May 2005 01:37, Duncan wrote:
> That isn't going to kill it for gcc-4.0.1-snapshots, right, only gcc-3.4?
> I'll be rather unhappy if the speed increases I've been attributing to
> that visibility support under gcc4, disappear! =8^(
It will be *completely* disabled.
-fvisibility=hidden *must not* be used if the project isn't supposed to use
only its own code without linking to other libraries, as that kills the RTTI
stuff.
It's not a fault in GCC, it's a fault in the way -fvisibility=hidden was used
by KDE.
KDE 3.5 and 4 will have the right visibility support enabled just for KDE
stuff instead of messing around with QT and other libraries which doesn't use
that consistently.
Please note that every try to use -fvisibility=hidden in CFLAGS will result in
*great* problems which won't be supported at all.
--
Diego "Flameeyes" Pettenò
Gentoo Developer (Gentoo/FreeBSD, Video, Gentoo/AMD64)
http://dev.gentoo.org/~flameeyes/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-26 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 16:48 [gentoo-dev] KDE 3.4 visibility support disabled Marcus D. Hanwell
2005-05-25 18:02 ` Jason Wever
2005-05-25 23:37 ` [gentoo-dev] " Duncan
2005-05-25 23:57 ` Diego 'Flameeyes' Pettenò [this message]
2005-05-26 4:25 ` [gentoo-dev] Re: [gentoo-amd64] " Dan Armak
2005-05-26 7:30 ` [gentoo-dev] " Duncan
2005-05-26 12:26 ` Caleb Tennis
2005-05-26 16:09 ` Andreas Fredriksson
2005-05-26 11:05 ` [gentoo-dev] " Marcus D. Hanwell
2005-05-26 23:23 ` [gentoo-dev] " Duncan
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=200505260157.56648@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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