TODO

1. remove unnecessary entry when there exists a trace that go back to this entry point 
2. gather number of function translated for each benchmark; 
1. if there are multiple inputs, calculates the average
2. use google doc to gather these data
3. trace guided layout has no influence for performance, why?
1. maybe wrong benchmarks, I've tried gcc, which one should I try?

QUESTION:

1. GCC, trace-method performs bad than method; Evidence shows that T-M used more than 4 times IBTC than method.  WHY???  The problem may be in the transition between 
1. Running test inputs and output trace profile; see what we got...
2. shit happen: how to stop optimization thread when execution thread logout...
3. Any IDEA?
4. It is because there is too many trace/method to build such that we still spend too much time on block fragment.

TODO:

1' prove that FP has been fix

2' prove trace-guilded layout works

3' prove partial inline works

3' prove chained partial inline works

Question:

gcc is strange: 1. does it trace-threshold-sensitive? 2. does it function-threshold-sensitive?