public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/46151] New: namespace versioning holes Date: Sat, 23 Oct 2010 17:23:00 -0000 [thread overview] Message-ID: <bug-46151-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46151 Summary: namespace versioning holes Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: bkoz@gcc.gnu.org In Zurich, Jason noticed a problem with namespace versioning and pointers to data types. This is the placeholder for a full description and analysis of this problem.
next reply other threads:[~2010-10-23 17:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-23 17:23 bkoz at gcc dot gnu.org [this message] 2010-10-23 19:53 ` [Bug libstdc++/46151] " jason at gcc dot gnu.org 2010-10-24 10:37 ` paolo.carlini at oracle dot com 2014-09-24 18:14 ` redi at gcc dot gnu.org 2014-09-24 19:46 ` jason at gcc dot gnu.org 2015-04-09 14:30 ` redi at gcc dot gnu.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=bug-46151-4@http.gcc.gnu.org/bugzilla/ \ --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).