public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19664] -fvisibility-inlines-hidden fails with gcc's extern template extension on amd64
Date: Sat, 29 Jan 2005 15:28:00 -0000 [thread overview]
Message-ID: <20050129152848.4977.qmail@sourceware.org> (raw)
In-Reply-To: <20050128064457.19664.andreas.pokorny@gmx.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-29 15:28 -------
(In reply to comment #8)
> I am also refereing to this example:
> http://gcc.gnu.org/ml/libstdc++/2005-01/msg00300.html
Now there is a libstdc++ bug for not using pop/push of the visibility in the headers which is not what I
orginally thought this bug was about.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19664
next prev parent reply other threads:[~2005-01-29 15:28 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 6:45 [Bug c++/19664] New: " andreas dot pokorny at gmx dot de
2005-01-28 9:56 ` [Bug c++/19664] " pcarlini at suse dot de
2005-01-28 13:02 ` lanius at gentoo dot org
2005-01-28 13:04 ` lanius at gentoo dot org
2005-01-28 13:13 ` pcarlini at suse dot de
2005-01-28 13:35 ` simon dot strandman at telia dot com
2005-01-28 14:19 ` [Bug target/19664] " pinskia at gcc dot gnu dot org
2005-01-29 1:05 ` hjl at lucon dot org
2005-01-29 13:05 ` pinskia at gcc dot gnu dot org
2005-01-29 15:09 ` andreas dot pokorny at gmx dot de
2005-01-29 15:26 ` andreas dot pokorny at gmx dot de
2005-01-29 15:28 ` pinskia at gcc dot gnu dot org [this message]
2005-01-29 15:33 ` [Bug libstdc++/19664] libstdc++ headers should have pop/push of the visibility around the declarations pinskia at gcc dot gnu dot org
2005-01-29 15:37 ` pinskia at gcc dot gnu dot org
2005-01-29 16:24 ` [Bug target/19664] " andreas dot pokorny at gmx dot de
2005-01-29 16:26 ` [Bug libstdc++/19664] " pinskia at gcc dot gnu dot org
2005-01-29 20:52 ` pcarlini at suse dot de
2005-01-31 10:32 ` pcarlini at suse dot de
2005-01-31 18:57 ` pcarlini at suse dot de
2005-02-02 13:51 ` pcarlini at suse dot de
2005-02-02 16:01 ` pcarlini at suse dot de
2005-02-02 16:09 ` hjl at lucon dot org
2005-02-02 16:16 ` pcarlini at suse dot de
2005-02-02 16:25 ` pcarlini at suse dot de
2005-02-02 17:18 ` hjl at lucon dot org
2005-02-06 10:20 ` [Bug c/19664] " giovannibajo@libero.it
2005-02-06 13:19 ` pcarlini@suse.de
2005-02-06 13:21 ` pcarlini@suse.de
2005-02-06 13:21 ` pcarlini@suse.de
2005-02-06 16:17 ` hjl@lucon.org
2005-02-08 13:55 ` [Bug libstdc++/19664] " hjl at lucon dot org
2005-02-26 18:32 ` bkoz at gcc dot gnu dot org
2005-02-27 12:49 ` giovannibajo at libero dot it
2005-02-27 14:52 ` hjl at lucon dot org
2005-04-18 12:49 ` matz at suse dot de
2005-04-18 12:50 ` matz at suse dot de
2005-04-18 14:14 ` pcarlini at suse dot de
2005-05-04 17:15 ` hjl at lucon dot org
2005-05-17 19:06 ` pcarlini at suse dot de
2005-05-17 21:39 ` pluto at agmk dot net
2005-05-17 21:40 ` mark at codesourcery dot com
2005-05-17 21:47 ` cvs-commit at gcc dot gnu dot org
2005-05-17 21:50 ` hjl at lucon dot org
2005-05-17 21:58 ` mark at codesourcery dot com
2005-05-17 22:00 ` pcarlini at suse dot de
2005-05-18 15:42 ` pluto at agmk dot net
2005-05-18 15:45 ` pcarlini at suse dot de
2005-05-19 10:02 ` bernie at develer dot com
2005-05-19 19:37 ` mark at codesourcery dot com
2005-05-20 8:35 ` lanius at gentoo dot org
2005-05-20 8:59 ` pluto at agmk dot net
2005-05-20 9:02 ` pluto at agmk dot net
2005-05-20 9:04 ` pcarlini at suse dot de
2005-05-20 18:48 ` mark at codesourcery dot com
2005-05-21 16:50 ` aj at suse dot de
2005-07-06 10:40 ` pcarlini at suse dot de
2005-07-14 17:02 ` pinskia at gcc dot gnu dot org
2005-07-21 16:18 ` pinskia at gcc dot gnu dot org
2005-08-21 20:26 ` hjl at lucon dot org
2005-08-29 20:58 ` pinskia at gcc dot gnu dot org
2005-08-29 22:24 ` geoffk 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=20050129152848.4977.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).