damn you overquoters..! :)
I think the right thing to do if for the JIT to do a scan to determine the actual end pc if the method's byte codes are greater than some limit, e.g. 1024 bytes of bytecodes. It then rejects the method if the actual end pc is greater than some limit that we find empirically causes the JIT to crash because of the size of the alloca.
yes. i think this is right way to do it. if method size is less than 1kb, then do wild guess, and if it larger, then do the scan.