public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "s_gccbugzilla at nedprod dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/15000] Support setting the default symbol visibility for ELF
Date: Wed, 28 Apr 2004 19:43:00 -0000	[thread overview]
Message-ID: <20040428182441.23189.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040418032536.15000.bryner@brianryner.com>


------- Additional Comments From s_gccbugzilla at nedprod dot com  2004-04-28 18:24 -------
(In reply to comment #20)
> Brian, nested classes aren't inheriting visibility off their enclosing class 
> with the new patch. I tried fixing this and failed because AFAICS in 
pushclass() 
> the enclosing class hasn't processed attribute flags yet and so everything is 
> always default visibility.
> 
> You know GCC better than I, so I'd appreciate it if you can find some 
solution. 
> Thereafter I think I have everything else covered, including the new pragma.

If we're not moving ahead with this angle, I can try merging aspects of the new 
patch with the old patch and rerelease. However AFAICS the method of storing 
data in the typeinfo is incapable of supporting the mechanics required for 
-fvisibility unless anyone has any suggestions?

Cheers,
Niall


-- 


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


  parent reply	other threads:[~2004-04-28 18:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-18  4:27 [Bug other/15000] New: " bryner at brianryner dot com
2004-04-18  8:16 ` [Bug other/15000] " pinskia at gcc dot gnu dot org
2004-04-18 13:37 ` bryner at brianryner dot com
2004-04-19  2:59 ` s_gccbugzilla at nedprod dot com
2004-04-19  3:16 ` s_gccbugzilla at nedprod dot com
2004-04-19  3:18 ` pinskia at gcc dot gnu dot org
2004-04-19 15:21 ` bryner at brianryner dot com
2004-04-19 21:29 ` s_gccbugzilla at nedprod dot com
2004-04-19 23:52 ` bryner at brianryner dot com
2004-04-20  1:05 ` s_gccbugzilla at nedprod dot com
2004-04-20  9:05 ` bryner at brianryner dot com
2004-04-22  2:42 ` s_gccbugzilla at nedprod dot com
2004-04-22  2:51 ` bryner at brianryner dot com
2004-04-22 18:40 ` s_gccbugzilla at nedprod dot com
2004-04-22 18:48 ` bryner at brianryner dot com
2004-04-22 20:37 ` s_gccbugzilla at nedprod dot com
2004-04-22 21:21 ` zack at codesourcery dot com
2004-04-23  5:31 ` s_gccbugzilla at nedprod dot com
2004-04-28 19:43 ` s_gccbugzilla at nedprod dot com [this message]
2004-05-03  2:36 ` bryner at brianryner dot com
2004-05-03  4:18 ` s_gccbugzilla at nedprod dot com
2004-05-05  6:52 ` s_gccbugzilla at nedprod dot com
2004-05-05  8:26 ` bryner at brianryner dot com
2004-05-05 20:38 ` s_gccbugzilla at nedprod dot com
2004-05-06  3:21 ` s_gccbugzilla at nedprod dot com
2004-05-11 17:08 ` s_gccbugzilla at nedprod dot com
2004-05-13 11:42 ` s_gccbugzilla at nedprod dot com
2004-05-30  1:43 ` s_gccbugzilla at nedprod dot com
2004-07-25 22:52 ` cvs-commit at gcc dot gnu dot org
2004-07-25 23:34 ` s_gccbugzilla at nedprod dot com
2004-07-25 23:36 ` pinskia at gcc dot gnu dot org
2004-07-25 23:57 ` giovannibajo at libero dot it
2004-07-26  1:31 ` s_gccbugzilla at nedprod dot com
2004-08-17  3:06 ` cvs-commit at gcc dot gnu dot org
2004-08-18 22:51 ` pinskia at gcc dot gnu dot org
2004-09-01 16:21 ` cvs-commit 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=20040428182441.23189.qmail@sources.redhat.com \
    --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).