libiberty: V3 ABI Java symbol demangling

Michael Sokolov msokolov@ivan.Harhan.ORG
Sat Jan 27 09:37:00 GMT 2001

Daniel Berlin <> wrote:

> Though we do do merges every so often from gcc->gdb (I would say
> overwrite, but unfortunately, I think there are a few small divergences)

I just did a diff and the only difference between gcc/libiberty and
src/libiberty was a bogus extraneous tab in src/libiberty/ChangeLog in the
blank line after the most recent entry. I have just committed the fix under the
obviously correct rule, so as of a few seconds ago the two libiberties are
*identical*. Yay!

> Do they exist?
> Anyone with libiberty access in the gcc repo should have it in the
> /cvs/src repo, I think.

I dunno. I don't think CVS allows write access to be controlled per module, so
everyone who has write access has it for the whole repo (/cvs/gcc or /cvs/src).
But there are still two repos, apparently with different folks approving people
for write access. I have write access to both repos because I was approved for
both GCC commit-after-approval and Binutils commit-after-approval,
independently by the respective maintainers. I know there are some people with
write access only to /cvs/src but not to /cvs/gcc, not sure the other way
around though.

> > Have DJ Delorie check libiberty patches into both  repos?
> Or me, or anyone with commit access to both.

Or me. :-) I would do anything that helps bring repo unification closer.

Michael Sokolov
Public Service Agent
International Engineering and Science Task Force

1351 VINE AVE APT 27		Phone: +1-714-738-5409
FULLERTON CA 92833-4291 USA	(home office)

E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP)

More information about the Java-patches mailing list