Re: Libjava failures status

[Andrew Haley <aph at cambridge dot redhat dot com>]

Jan Hubicka writes:
 > > Jan Hubicka wrote:
 > > 
 > > >Now, at least according to the internal check, we maitain the BB
 > > >boundaries consistent and we should reorder over them.  I plan
 > > >to add symetrical check verifying that we do not discover
 > > >trapping instruciton in the middle of basic block - so far I am
 > > >just checking that if there is EH edge there is trapping
 > > >instruction just before it.
 > > >
 > > 
 > > It would be nice if we could avoid pessimising this too much. eg given:
 > > 
 > > a = foo.a;
 > > b = foo.b;
 > > 
 > > Then obviously the second load from foo can not trap.

Um, how do you know what order the memory accesses happen in?  There's
nothing to stop sched from moving them around.

 > > I assume that would allow for larger BBs and that is good for
 > > optimization.
 > 
 > Concerning the memory traps, Java has references and bounding
 > checks on arrays.  How can one even access trapping memory in Java?

Integer i = null;
System.out.print (i);

Andrew.