| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
llvm-svn: 199275
|
|
|
|
| |
llvm-svn: 199268
|
|
|
|
|
|
|
|
|
|
|
|
| |
MCJIT remote execution (ChildTarget+RemoteTargetExternal) protocol was in
dire need of refactoring. It was fail-prone, had no error reporting and
implemented the same message logic on every single function.
This patch rectifies it, and makes it work on ARM, where it was randomly
failing. Other architectures shall profit from this change as well, making
their buildbots and releases more reliable.
llvm-svn: 199261
|
|
|
|
| |
llvm-svn: 199080
|
|
|
|
| |
llvm-svn: 198929
|
|
|
|
| |
llvm-svn: 198928
|
|
|
|
| |
llvm-svn: 198927
|
|
|
|
|
|
| |
new in C++11.
llvm-svn: 198853
|
|
|
|
|
|
|
|
|
|
|
| |
root path to which object files managed by the LLIObjectCache instance should be
written. This option defaults to "", in which case objects are cached in the
same directory as the bitcode they are derived from.
The load-object-a.ll test has been rewritten to use this option to support
testing in environments where the test directory is not writable.
llvm-svn: 198852
|
|
|
|
| |
llvm-svn: 198821
|
|
|
|
|
|
|
|
|
| |
I believe the bot failures on linux systems were due to overestimating the
alignment of object-files within archives, which are only guaranteed to be
two-byte aligned. I have reduced the alignment in
RuntimeDyldELF::createObjectImageFromFile accordingly.
llvm-svn: 198737
|
|
|
|
|
|
| |
Unused variable and unused typedef in release build.
llvm-svn: 196947
|
|
|
|
| |
llvm-svn: 196908
|
|
|
|
|
|
| |
It depends on nothing described in LLVM_LINK_COMPONENTS.
llvm-svn: 196902
|
|
|
|
| |
llvm-svn: 196654
|
|
|
|
| |
llvm-svn: 196641
|
|
|
|
|
|
| |
Patch by Andy Kaylor, with minor edits to resolve merge conflicts.
llvm-svn: 196639
|
|
|
|
|
|
| |
Unused typedefs and unused variables.
llvm-svn: 196526
|
|
|
|
| |
llvm-svn: 196447
|
|
|
|
| |
llvm-svn: 193571
|
|
|
|
| |
llvm-svn: 193570
|
|
|
|
| |
llvm-svn: 193552
|
|
|
|
| |
llvm-svn: 193544
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Mark tests as XFAIL:cygming in test/ExecutionEngine/MCJIT/remote.
Rather to suppress them, I'd like to leave them running as XFAIL.
- Revert r193472. RecordMemoryManager no longer resolves __main on cygming.
There are a couple of issues.
- X86 Codegen emits "call __main" in @main for targeting cygming.
It is useless in JIT. FYI, tests are passing when emitting __main is disabled.
- Current remote JIT does not resolve any symbols in child context.
FIXME: __main should be disabled, or remote JIT should resolve __main.
llvm-svn: 193498
|
|
|
|
|
|
| |
unbreak mingw32.
llvm-svn: 193472
|
|
|
|
|
|
| |
Patch by Yaron Keren
llvm-svn: 192753
|
|
|
|
|
|
|
|
| |
This fixes a problem from a previous check-in where a return value was omitted.
Previously the remote/stubs-remote.ll and remote/stubs-sm-pic.ll tests were reporting passes, but they should have been failing. Those tests attempt to link against an external symbol and remote symbol resolution is not supported. The old RemoteMemoryManager implementation resulted in local symbols being used for resolution and the child process crashed but the test didn't notice. With this check-in remote symbol resolution fails, and so the test (correctly) fails.
llvm-svn: 192514
|
|
|
|
| |
llvm-svn: 192504
|
|
|
|
| |
llvm-svn: 192205
|
|
|
|
| |
llvm-svn: 192031
|
|
|
|
| |
llvm-svn: 191979
|
|
|
|
| |
llvm-svn: 191976
|
|
|
|
|
|
|
| |
This is unlikely to ever fail, but ubuntu GCC warns when the return value is
unused.
llvm-svn: 191973
|
|
|
|
| |
llvm-svn: 191938
|
|
|
|
| |
llvm-svn: 191861
|
|
|
|
| |
llvm-svn: 191857
|
|
|
|
|
|
| |
searching $PATH for it then blindly executing it from $PWD anyway.
llvm-svn: 191856
|
|
|
|
| |
llvm-svn: 191848
|
|
|
|
| |
llvm-svn: 191845
|
|
|
|
| |
llvm-svn: 191844
|
|
|
|
|
|
|
|
| |
At this time only Unix-based systems are supported. Windows has stubs and should re-route to the simulated mode.
Thanks to Sriram Murali for contributions to this patch.
llvm-svn: 191843
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
APIs, both in C++ and C land.
It's useful for the memory managers that are allocating a section to know what the name of the section is.
At a minimum, this is useful for low-level debugging - it's customary for JITs to be able to tell you what
memory they allocated, and as part of any such dump, they should be able to tell you some meta-data about
what each allocation is for. This allows clients that supply their own memory managers to do this.
Additionally, we also envision the SectionName being useful for passing meta-data from within LLVM to an LLVM
client.
This changes both the C and C++ APIs, and all of the clients of those APIs within LLVM. I'm assuming that
it's safe to change the C++ API because that API is allowed to change. I'm assuming that it's safe to change
the C API because we haven't shipped the API in a release yet (LLVM 3.3 doesn't include the MCJIT memory
management C API).
llvm-svn: 191804
|
|
|
|
|
|
|
|
| |
Tests to follow.
PIC with small code model and EH frame handling will not work with multiple modules. There are also some rough edges to be smoothed out for remote target support.
llvm-svn: 191722
|
|
|
|
|
|
|
| |
were not provided.
FIXME: Would it be responsible to provide GOT?
llvm-svn: 188855
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- warn users when -debug-ir is used with old JIT engine (only partial debug
info is available)
For example, to debug an IR file with GDB (that supports JIT registration), do:
$ gdb --args lli -use-mcjit -debug-ir testcase.ll
(gdb) break main
(gdb) run
<Process continues to lli main>
(gdb) continue
<Process continues to testcase.ll main()
(gdb) step
<Now stepping through the LLVM IR in testcase.ll>
llvm-svn: 185197
|
|
|
|
|
|
|
|
| |
On 32-bit hosts %p can print garbage when given a uint64_t, we should
use %llx instead. This only affects the output of the debugging text
produced by lli.
llvm-svn: 182209
|
|
|
|
|
|
|
| |
the JIT object (including XFAIL an ARM test that now needs fixing). Also renames
internal function for consistency.
llvm-svn: 182085
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
EngineBuilder interface required a JITMemoryManager even if it was being used
to construct an MCJIT. But the MCJIT actually wants a RTDyldMemoryManager.
Consequently, the SectionMemoryManager, which is meant for MCJIT, derived
from the JITMemoryManager and then stubbed out a bunch of JITMemoryManager
methods that weren't relevant to the MCJIT.
This patch fixes the situation: it teaches the EngineBuilder that
RTDyldMemoryManager is a supertype of JITMemoryManager, and that it's
appropriate to pass a RTDyldMemoryManager instead of a JITMemoryManager if
we're using the MCJIT. This allows us to remove the stub methods from
SectionMemoryManager, and make SectionMemoryManager a direct subtype of
RTDyldMemoryManager.
llvm-svn: 181820
|
|
|
|
| |
llvm-svn: 181354
|
|
|
|
|
|
|
|
|
|
|
| |
that work on the LLVMBuild based dependency specification didn't
actually work, we just now maintain dependencies in *3* places instead
of 2. Yay.
There may still be some missing dependencies, I'm still sifting through
the bots and my builds, but this is a step in the right direction.
llvm-svn: 177988
|