Yuri wrote: > Andrew Haley wrote: >> Yes, we should update that. There hasn't been a lot of new gcj >> development, >> but it is maintained. >>>>>>> Also I submitted few PRs a month ago and there is no response at all. >>>>>>> Which ones? >>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41356 > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41361 Can't reproduce this. This is presumably a bug in the FreeBSD port of gcj. I'm not sure who maintains gcj on FreeBSD. > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41372 > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41375 > And today I added one more: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41745 All of these seem to be FreeBSD specific. I think that the FreeBSD port must be broken. The best plan is to build gcj from source and run the libgcj test suite. Then we'll know how brain-damaged the FreeBSD port really is. Andrew.