public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bugzilla at seibutsu dot mailsnare dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/28474] New: mangle_name.c mangles names unecessarily Date: Mon, 24 Jul 2006 21:04:00 -0000 [thread overview] Message-ID: <bug-28474-13002@http.gcc.gnu.org/bugzilla/> (raw) There is a bug in mangle_name.c which leads to mangling any name containing two underscores followed by a capital "U", even if those three characters are not consecutive. For example, the following program will not link: [begin Test.java] public class Test { public static final native void x_y_NewUser(); public static final native void xy__User(); public static void main(String[] args) { x_y_NewUser(); xy__User(); } } [end Test.java] [begin natTest.cpp] #include "Test.h" void Test::x_y_NewUser() { return; } void Test::xy__User() { return; } [end natTest.cpp] I will attach a patch which fixes the first case but not the second (since I'm not sure how the second case was intended to be handled). -- Summary: mangle_name.c mangles names unecessarily Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gcc-bugzilla at seibutsu dot mailsnare dot net GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28474
next reply other threads:[~2006-07-24 21:04 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-24 21:04 gcc-bugzilla at seibutsu dot mailsnare dot net [this message] 2006-07-24 21:07 ` [Bug java/28474] " gcc-bugzilla at seibutsu dot mailsnare dot net 2008-08-22 1:03 ` mhesseli at fulcrummicro dot com 2009-10-20 16:02 ` aph 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=bug-28474-13002@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).