public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: daney@sourceware.org To: src-cvs@sourceware.org Subject: src/libiberty ChangeLog cp-demangle.c testsuit ... Date: Sun, 27 Jan 2008 06:25:00 -0000 [thread overview] Message-ID: <20080127062544.24401.qmail@sourceware.org> (raw) CVSROOT: /cvs/src Module name: src Changes by: daney@sourceware.org 2008-01-27 06:25:44 Modified files: libiberty : ChangeLog cp-demangle.c libiberty/testsuite: demangle-expected Log message: include/ 2008-01-26 David Daney <ddaney@avtrex.com> * demangle.h (demangle_component_type): Add DEMANGLE_COMPONENT_JAVA_RESOURCE, DEMANGLE_COMPONENT_COMPOUND_NAME, and DEMANGLE_COMPONENT_CHARACTER as new enum values. (demangle_component): Add struct s_character to union u. libiberty/ 2008-01-26 David Daney <ddaney@avtrex.com> * cp-demangle.c (d_dump): Handle DEMANGLE_COMPONENT_JAVA_RESOURCE, DEMANGLE_COMPONENT_COMPOUND_NAME, and DEMANGLE_COMPONENT_CHARACTER cases. (d_make_comp): Handle DEMANGLE_COMPONENT_COMPOUND_NAME and DEMANGLE_COMPONENT_JAVA_RESOURCE cases. (d_make_character): New function. (d_java_resource): Same. (d_special_name): Handle "Gr" case. (d_print_comp): Handle DEMANGLE_COMPONENT_JAVA_RESOURCE, DEMANGLE_COMPONENT_COMPOUND_NAME, and DEMANGLE_COMPONENT_CHARACTER cases. * testsuite/demangle-expected: Add test for java resource name mangling. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/libiberty/ChangeLog.diff?cvsroot=src&r1=1.444&r2=1.445 http://sourceware.org/cgi-bin/cvsweb.cgi/src/libiberty/cp-demangle.c.diff?cvsroot=src&r1=1.69&r2=1.70 http://sourceware.org/cgi-bin/cvsweb.cgi/src/libiberty/testsuite/demangle-expected.diff?cvsroot=src&r1=1.37&r2=1.38
next reply other threads:[~2008-01-27 6:25 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-27 6:25 daney [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-07-02 19:47 jkratoch 2011-07-02 19:45 jkratoch 2011-07-01 17:30 jkratoch 2010-11-16 17:58 hjl 2010-11-16 14:49 ian 2010-09-10 22:42 tromey 2010-06-10 15:42 jakub 2007-05-06 0:25 geoffk 2007-03-16 1:09 geoffk 2005-05-25 23:32 rth
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=20080127062544.24401.qmail@sourceware.org \ --to=daney@sourceware.org \ --cc=src-cvs@sourceware.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).