http://llvm.org https://git.amat.us/llvm/atom/lib/ExecutionEngine?h=release_32 2012-12-04T20:23:05Z 2012-12-04T20:23:05Z Pawel Wodnicki pawel@32bitmicro.com 2012-12-04T20:23:05Z urn:sha1:7d2093c741f929a65f2ae0de261872cb7dc8cdba Merging r169183: RuntimeDyld: Fix up r169178. MSVC doesn't like "or". Merging r169178: Runtime dynamic linker for MCJIT should support MIPS BigEndian architecture. This small change adds support for that. It will make all MCJIT tests pass in make-check on BigEndian platforms. Patch by Petar Jovanovic. Merging r169177: Classic JIT is still being supported by MIPS, along with MCJIT. This change adds endian-awareness to MipsJITInfo and emitWordLE in MipsCodeEmitter has become emitWord now to support both endianness. Patch by Petar Jovanovic. Merging r169174: Functions in MipsCodeEmitter.cpp that expand unaligned loads/stores are dead code. Removing it. Patch by Petar Jovanovic. git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_32@169296 91177308-0d34-0410-b5e6-96231b3b80d8 2012-11-06T19:06:46Z Andrew Kaylor andrew.kaylor@intel.com 2012-11-06T19:06:46Z urn:sha1:a082892fb734f4738f5e687778997706fa0dd65a git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167477 91177308-0d34-0410-b5e6-96231b3b80d8 2012-11-06T18:51:59Z Andrew Kaylor andrew.kaylor@intel.com 2012-11-06T18:51:59Z urn:sha1:776054dd938472828ac3ebf75b05e21171ef4ecf This patch adds the interface to expose events from MCJIT when an object is emitted or freed and implements the MCJIT functionality to send those events. The IntelJITEventListener implementation is left empty for now. It will be fleshed out in a future patch. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167475 91177308-0d34-0410-b5e6-96231b3b80d8 2012-11-05T20:57:16Z Andrew Kaylor andrew.kaylor@intel.com 2012-11-05T20:57:16Z urn:sha1:28989889bf3aa3314562d438aece245b71176ec4 Prior to this patch RuntimeDyld attempted to re-apply relocations every time reassignSectionAddress was called (via MCJIT::mapSectionAddress). In addition to being inefficient and redundant, this led to a problem when a section was temporarily moved too far away from another section with a relative relocation referencing the section being moved. To fix this, I'm adding a new method (finalizeObject) which the client can call to indicate that it is finished rearranging section addresses so the relocations can safely be applied. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167400 91177308-0d34-0410-b5e6-96231b3b80d8 2012-11-02T19:45:23Z Andrew Kaylor andrew.kaylor@intel.com 2012-11-02T19:45:23Z urn:sha1:a307a1cf859f4a523951ac887d094039547adeb5 Some ELF relocations require adding the a value to the original contents of the object buffer at the specified location. In order to properly handle multiple applications of a relocation, the RuntimeDyld code should be grabbing the original value from the object buffer and writing a new value into the loaded section buffer. This patch changes the parameters passed to resolveRelocations to accommodate this need. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167304 91177308-0d34-0410-b5e6-96231b3b80d8 2012-11-01T19:49:21Z Andrew Kaylor andrew.kaylor@intel.com 2012-11-01T19:49:21Z urn:sha1:5fc8c7cb8571f99b69264aeba48c45eed1c69f6a git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167247 91177308-0d34-0410-b5e6-96231b3b80d8 2012-11-01T09:14:31Z Chandler Carruth chandlerc@gmail.com 2012-11-01T09:14:31Z urn:sha1:426c2bf5cdd2173e4a33aea8cb92cf684a724f4b r165941: Resubmit the changes to llvm core to update the functions to support different pointer sizes on a per address space basis. Despite this commit log, this change primarily changed stuff outside of VMCore, and those changes do not carry any tests for correctness (or even plausibility), and we have consistently found questionable or flat out incorrect cases in these changes. Most of them are probably correct, but we need to devise a system that makes it more clear when we have handled the address space concerns correctly, and ideally each pass that gets updated would receive an accompanying test case that exercises that pass specificaly w.r.t. alternate address spaces. However, from this commit, I have retained the new C API entry points. Those were an orthogonal change that probably should have been split apart, but they seem entirely good. In several places the changes were very obvious cleanups with no actual multiple address space code added; these I have not reverted when I spotted them. In a few other places there were merge conflicts due to a cleaner solution being implemented later, often not using address spaces at all. In those cases, I've preserved the new code which isn't address space dependent. This is part of my ongoing effort to clean out the partial address space code which carries high risk and low test coverage, and not likely to be finished before the 3.2 release looms closer. Duncan and I would both like to see the above issues addressed before we return to these changes. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167222 91177308-0d34-0410-b5e6-96231b3b80d8 2012-11-01T00:46:04Z Andrew Kaylor andrew.kaylor@intel.com 2012-11-01T00:46:04Z urn:sha1:647d6d7d3b6bfc8d99b8425cff50f979dbbd2ab6 Patch by Ashok Thirumurthi git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167192 91177308-0d34-0410-b5e6-96231b3b80d8 2012-10-30T22:21:55Z Eli Friedman eli.friedman@gmail.com 2012-10-30T22:21:55Z urn:sha1:bbc6e671b1a902c96aff152cc524a5ee6e253907 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167057 91177308-0d34-0410-b5e6-96231b3b80d8 2012-10-29T10:47:04Z Tim Northover Tim.Northover@arm.com 2012-10-29T10:47:04Z urn:sha1:f00677d74f1be5b4c7c73e1681a64c9062f4c7ee Patch by Amara Emerson. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@166919 91177308-0d34-0410-b5e6-96231b3b80d8