public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mhesseli at fulcrummicro dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/28474] mangle_name.c mangles names unecessarily
Date: Fri, 22 Aug 2008 01:03:00 -0000	[thread overview]
Message-ID: <20080822010137.17452.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28474-13002@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from mhesseli at fulcrummicro dot com  2008-08-22 01:01 -------
Over the past month I have been trying to make a largish Java project
accessible from Perl using SWIG and GCJ. I have been very pleased with the way
GCJ allowed me to accomplish this. Unfortunately, late in the project I was hit
by this bug; several of the enumerations used in the Java code contained
uppercase U's which were converted to _U (underscore followed by uppercase U).
This eventually resulted in linking errors.

The patch attached to this bug solved the issue on GCC 4.3.1. I would therefore
like to add my vote for this patch to be submitted to what is going to be GCC
4.4.


-- 

mhesseli at fulcrummicro dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mhesseli at fulcrummicro dot
                   |                            |com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28474


  parent reply	other threads:[~2008-08-22  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24 21:04 [Bug java/28474] New: " gcc-bugzilla at seibutsu dot mailsnare dot net
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 [this message]
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=20080822010137.17452.qmail@sourceware.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: link
Be 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).