public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/20303] New: Can't push more than 16 nested visibility Date: Thu, 03 Mar 2005 18:20:00 -0000 [thread overview] Message-ID: <20050303182015.20303.hjl@lucon.org> (raw) When #pragma GCC visibility push(default) #pragma GCC visibility pop are used for header file wrappers, we may have more 16 #pragma GCC visibility push(default) Currently gcc will fail. -- Summary: Can't push more than 16 nested visibility Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl at lucon dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20303
next reply other threads:[~2005-03-03 18:20 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-03 18:20 hjl at lucon dot org [this message] 2005-03-03 18:43 ` [Bug c/20303] " pinskia at gcc dot gnu dot org 2005-03-03 18:47 ` hjl at lucon dot org 2005-03-03 19:19 ` hjl at lucon dot org 2005-03-03 22:58 ` joseph at codesourcery dot com 2005-03-03 23:00 ` giovannibajo at libero dot it 2005-04-05 18:41 ` hjl at lucon dot org 2005-05-30 18:51 ` cvs-commit at gcc dot gnu dot org 2005-05-30 18:52 ` hjl at lucon dot org 2005-05-30 18:53 ` hjl at lucon dot org 2005-05-30 18:56 ` pinskia at gcc dot gnu dot org 2005-07-14 15:37 ` jakub at redhat dot com 2005-07-14 17:25 ` [Bug c/20303] [4.0 only] " hjl at lucon dot org 2005-07-14 17:36 ` hjl at lucon dot org 2005-07-15 21:52 ` pinskia at gcc dot gnu dot org 2005-07-25 7:46 ` cvs-commit at gcc dot gnu dot org 2005-09-27 16:15 ` mmitchel 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=20050303182015.20303.hjl@lucon.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: 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).