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: Mon, 03 May 2004 04:18:00 -0000 [thread overview] Message-ID: <20040503041816.11621.qmail@sources.redhat.com> (raw) In-Reply-To: <20040418032536.15000.bryner@brianryner.com> ------- Additional Comments From s_gccbugzilla at nedprod dot com 2004-05-03 04:18 ------- (In reply to comment #22) > I'd be surprised if that happens with the old patch, either... certainly it's > not something I've tested. (The old patch always initializes a new class on the > class stack with VISIBILITY_DEFAULT, so I don't see how the visibility would > come from anywhere other than the inner class's attributes). > > I'm not really sure how to make it work, either... I'd need to think about it > some more. I could have sworn that my old test piece of code tested this and it worked (unfortunately I must have deleted it as I can't find it now). However testing my patch based on your old one shows that I am quite wrong and indeed the original patch didn't do it either. I must be getting old :( Nevertheless the sentiment remains good I think - classes should inherit their visibility off their enclosing class when present. I'm a little busy right now but I intend to get onto this sometime this week. It seems to me that the visibility can't be stored in the typeinfo if that isn't available at the point of constructing nested class decls unless some (probably complex) machinery is used to propagate any class settings through all nested class' typeinfos too (I can't see how to easily obtain a list of nested classes other than iterate through everything which seems inefficient). If your thoughts yield anything, please do let me know lest we reinvent the wheel! Cheers, Niall -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15000
next prev parent reply other threads:[~2004-05-03 4:18 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 2004-05-03 2:36 ` bryner at brianryner dot com 2004-05-03 4:18 ` s_gccbugzilla at nedprod dot com [this message] 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=20040503041816.11621.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: linkBe 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).