public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: sdouglass@arm.com To: gcc-gnats@gcc.gnu.org Cc: rearnsha@arm.com Subject: c++/6548: Incorrect mangling for extern C and namespace Date: Fri, 03 May 2002 07:56:00 -0000 [thread overview] Message-ID: <20020503144635.20332.qmail@sources.redhat.com> (raw) >Number: 6548 >Category: c++ >Synopsis: Incorrect mangling for extern C and namespace >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri May 03 07:56:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Scott Douglass >Release: gcc-3.0.4 and later (still present in trunk) >Organization: >Environment: All >Description: Neither N::x' nor 'N::y' should be mangled in the example below but 'N::x' does get mangled. The work-around is to use the variable in a non-inline function as is done with 'N::y'. This example works in 2.95.2, because the namespace is never mangled by 2.95.2. >How-To-Repeat: Compile the following code: extern "C" { namespace N { extern int x,y;} } int N::x = 42; // I'm incorrectly mangled int f() { return N::y; } int N::y = 43; // I'm correctly not mangled >Fix: Unknown >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-03 14:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-03 7:56 sdouglass [this message] 2002-06-05 7:57 lerdsuwa
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=20020503144635.20332.qmail@sources.redhat.com \ --to=sdouglass@arm.com \ --cc=gcc-gnats@gcc.gnu.org \ --cc=rearnsha@arm.com \ /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).