current gcjx status

Mon Mar 28 22:26:00 GMT 2005

Tom Tromey wrote:
> Per> One performance bug, I think, in the current front-end is that
> Per> it reads too many classes.
> ... 
> Per> I don't know how well gcjx does in this respect - but jc1 seems
> Per> to be doing a very bad job.
>> There should be no real difference here between jc1 and gcjx, I think.
> It is probably a generic gcjx bug.

I'm not sure what you're saying there. I'm suggesting this is a place
where perhaps gcjx can be smarter that jc1 currently is. I wasn't
specifically addressing your concern about gcjx's current slowness.
Rather, it was a "by the way, you might want to keep this in mind"
note, if you haven't.
-- 
	--Per Bothner
per@bothner.com http://per.bothner.com/