I think that I have found a way to rebuild a virtual stack of inlined functions. This commit just adds few code able to rebuild this stack in the safepoint generator.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200650 91177308-0d34-0410-b5e6-96231b3b80d8
Rename safepoint.cc

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200651 91177308-0d34-0410-b5e6-96231b3b80d8
A function to emit function names (char*)

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200653 91177308-0d34-0410-b5e6-96231b3b80d8
Store inline information in safepoints.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200657 91177308-0d34-0410-b5e6-96231b3b80d8
getJavaCaller takes into account inlining.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200658 91177308-0d34-0410-b5e6-96231b3b80d8
Native printStackTrace (if a problem occurs during bootstrap) also takes into account inlining.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200660 91177308-0d34-0410-b5e6-96231b3b80d8
Add a helper function to build stack traces.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200663 91177308-0d34-0410-b5e6-96231b3b80d8
openjdk stack trace management takes into account inlining.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200669 91177308-0d34-0410-b5e6-96231b3b80d8
Prepare the reading of the code attributes.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200689 91177308-0d34-0410-b5e6-96231b3b80d8
Fix a dependency beg in Makefile.rules.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200690 91177308-0d34-0410-b5e6-96231b3b80d8
Inspect LineAttribute to find the line numbers.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200691 91177308-0d34-0410-b5e6-96231b3b80d8
Aggressive inline seems ok.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200692 91177308-0d34-0410-b5e6-96231b3b80d8
Better heuristic for inlining (basically, the previous one was buggy:))

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200831 91177308-0d34-0410-b5e6-96231b3b80d8
Stack size is now fixed (important for inlining)

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200834 91177308-0d34-0410-b5e6-96231b3b80d8
Continue the simplification of Thread::get()

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200835 91177308-0d34-0410-b5e6-96231b3b80d8
Do not directly see anymore TLS computation in j3codegen.cc

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200836 91177308-0d34-0410-b5e6-96231b3b80d8
monitor enter and monitor exit are now only written in C++ and inlined in JITted code.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200846 91177308-0d34-0410-b5e6-96231b3b80d8
Monitor enter and monitor exit are now instance methods.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200847 91177308-0d34-0410-b5e6-96231b3b80d8
Remove the useless j3thread::get(void*) function

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200848 91177308-0d34-0410-b5e6-96231b3b80d8
Cleanup the code.

git-svn-id: http://llvm.org/svn/llvm-project/vmkit/branches/mcjit@200851 91177308-0d34-0410-b5e6-96231b3b80d8