On Sun, Jun 22, 2008 at 4:04 AM, Richard Kenner <[EMAIL PROTECTED]> wrote: >> > An interesting question that I see as relevant here and for which I have no >> > data is: what percentage of the time does a patch cause an error *only* >> > in libjava? I think you have to weigh the cost of the build of that >> > library against the number of bugs that it finds. >> >> Happened to me multiple times. > > Is there a way to characterize the kinds of changes that are more likely > to make this happen? We see this with Ada, for example: many middle-end > developers by now know which changes are most likely to potentially affect > Ada and do an Ada build too for those cases. Would this sort of approach > work for Java as well?
libjava adds quite an amount of coverage on the general optimizers. Most of the time this was ICEs and miscompiles only happening for libjava but not in the C/C++ testsuite. Richard.
