aboutsummaryrefslogtreecommitdiff
path: root/llvm/bindings/python
AgeCommit message (Collapse)AuthorFilesLines
2015-12-18Deprecate a few C APIs.Rafael Espindola1-5/+4
This deprecates: * LLVMParseBitcode * LLVMParseBitcodeInContext * LLVMGetBitcodeModuleInContext * LLVMGetBitcodeModule They are replaced with the functions with a 2 suffix which do not record a diagnostic. llvm-svn: 256065
2015-08-18[PM/AA] Remove the last relics of the separate IPA library from LLVM,Chandler Carruth1-4/+0
folding the code into the main Analysis library. There already wasn't much of a distinction between Analysis and IPA. A number of the passes in Analysis are actually IPA passes, and there doesn't seem to be any advantage to separating them. Moreover, it makes it hard to have interactions between analyses that are both local and interprocedural. In trying to make the Alias Analysis infrastructure work with the new pass manager, it becomes particularly awkward to navigate this split. I've tried to find all the places where we referenced this, but I may have missed some. I have also adjusted the C API to continue to be equivalently functional after this change. Differential Revision: http://reviews.llvm.org/D12075 llvm-svn: 245318
2015-07-06Remove getRelocationAddress.Rafael Espindola1-11/+0
Originally added in r139314. Back then it didn't actually get the address, it got whatever value the relocation used: address or offset. The values in different object formats are: * MachO: Always an offset. * COFF: Always an address, but when talking about the virtual address of sections it says: "for simplicity, compilers should set this to zero". * ELF: An offset for .o files and and address for .so files. In the case of the .so, the relocation in not linked to any section (sh_info is 0). We can't really compute an offset. Some API mappings would be: * Use getAddress for everything. It would be quite cumbersome. To compute the address elf has to follow sh_info, which can be corrupted and therefore the method has to return an ErrorOr. The address of the section is also the same for every relocation in a section, so we shouldn't have to check the error and fetch the value for every relocation. * Use a getValue and make it up to the user to know what it is getting. * Use a getOffset and: * Assert for dynamic ELF objects. That is a very peculiar case and it is probably fair to ask any tool that wants to support it to use ELF.h. The only tool we have that reads those (llvm-readobj) already does that. The only other use case I can think of is a dynamic linker. * Check that COFF .obj files have sections with zero virtual address spaces. If it turns out that some assembler/compiler produces these, we can change COFFObjectFile::getRelocationOffset to subtract it. Given COFF format, this can be done without the need for ErrorOr. The getRelocationAddress method was never implemented for COFF. It also had exactly one use in a very peculiar case: a shortcut for adding the section value to a pcrel reloc on MachO. Given that, I don't expect that there is any use out there of the C API. If that is not the case, let me know and I will add it back with the implementation inlined and do a proper deprecation. llvm-svn: 241450
2014-04-25[python] Fix getting section contents.Anders Waldenborg2-2/+12
The returnvalue was handled as c_char_p which ment that ctypes handled it as a NUL-terminated string making it cut the contents at first NUL (or even worse - overrunning the buffer if it doesn't contain a NUL). Differential Revision: http://reviews.llvm.org/D3474 llvm-svn: 207199
2014-04-23[python] Fix python bindings testsAnders Waldenborg1-1/+0
Broke after the changes related to the LLVMGetSymbolFileOffset removal in r206750 llvm-svn: 207018
2014-04-21Convert getFileOffset to getOffset and move it to its only user.Rafael Espindola1-12/+0
We normally don't drop functions from the C API's, but in this case I think we can: * The old implementation of getFileOffset was fairly broken * The introduction of LLVMGetSymbolFileOffset was itself a C api breaking change as it removed LLVMGetSymbolOffset. * It is an incredibly specialized use case. The only reason MCJIT needs it is because of its odd position of being a dynamic linker of .o files. llvm-svn: 206750
2014-02-23[python-bindings] Remove some cruft that snuck in.Michael Gottesman1-4/+2
llvm-svn: 201966
2014-02-22[python-bindings] Added OpCode like support for all enumerations with unittests.Michael Gottesman2-37/+139
Also fixed some trailing whitespace issues. llvm-svn: 201929
2013-12-20Fix documentation typosAlp Toker1-2/+2
llvm-svn: 197757
2013-11-17python: Fix check for disasm creation failureAnders Waldenborg2-1/+5
Check should be for pointer being NULL, not what it points to. Also adds a test for this case. Reviewed By: indygreg Differential Revision: http://llvm-reviews.chandlerc.com/D1878 llvm-svn: 194965
2013-11-17python: Properly initialize before trying to create disasmAnders Waldenborg1-0/+26
As the "LLVMInitializeAll*" functions are not available as symbols in the shared library they can't be used, and as a workaround a list of the targets is kept and the individual symbols tried. As soon as the "All"-functions are changed to proper symbols (as opposed to static inlines in the headers) this hack will be replace with simple calls to the corresponding "LLVMInitializeAll*" functions. Reviewed By: indygreg CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D1879 llvm-svn: 194964
2013-09-11[python-bindings] Added support for getting/setting operands of values and ↵Michael Gottesman2-3/+39
getting the number of operands of a value. Also in the process did some cleanups for BasicBlock. llvm-svn: 190477
2013-09-11[python-bindings] Added support for iterating over a basic blocks ↵Michael Gottesman2-0/+99
instructions, getting their name/dumping them, f/b iteration. Tests are included. llvm-svn: 190475
2013-09-11[python-bindings] Added support for iterating over a function's basic ↵Michael Gottesman2-0/+105
blocks, dumping/getting names of those bb, f/w iteration. Tests are included. llvm-svn: 190473
2013-09-11[python-bindings] Added support for getting a module's functions, iterating ↵Michael Gottesman2-0/+101
f/b over said functions, dumping/print name of functions. Tests are included as well. llvm-svn: 190471
2013-09-11[python-bindings] Export OpCode from core.py.Michael Gottesman1-0/+1
llvm-svn: 190468
2013-09-11[python-bindings] Added test for reading a module from bitcode.Michael Gottesman1-0/+15
llvm-svn: 190467
2013-09-11[python-bindings] Fixed 3 test failures caused by typos.Michael Gottesman2-4/+6
llvm-svn: 190465
2013-09-11Fixed typo.Michael Gottesman1-3/+3
llvm-svn: 190459
2013-09-11[python-bindings] Added code for loading a module from bitcode, getset its ↵Michael Gottesman5-0/+128
datalayout, getset its target, dump it, print it to a file. llvm-svn: 190458
2013-09-11[python-bindings] Added bindings for LLVMContextRef and a test for creating ↵Michael Gottesman2-0/+29
a new context or getting the global context. llvm-svn: 190457
2013-09-11[python-bindings] Implemented the PassRegistry class and the calls to ↵Michael Gottesman2-0/+72
initialize/shutdown llvm. Also included an initialize_llvm declaration. llvm-svn: 190456
2013-09-11[python-bindings] Removed unused import byref from llvm/disassembler.py.Michael Gottesman1-1/+0
llvm-svn: 190455
2013-09-10[python-bindings] Changed test_memory_buffer_create_from_file to just use ↵Michael Gottesman1-1/+1
the generic provided test_file instead of a binary. llvm-svn: 190389
2013-09-10[python bindings] Added code to get the length of a memory buffer. Tests are ↵Michael Gottesman4-0/+14
included. This is a part of a series of patches that have been sitting fallow on a personal branch that I have been messing with for a bit. The patches start to flesh out the python llvm-c wrapper to the point where you can: 1. Load Modules from Bitcode/Dump/Print them. 2. Iterate over Functions from those modules/get their names/dump them. 3. Iterate over the BasicBlocks from said function/get the BB's name/dump it. 4. Iterate over the Instructions in said BasicBlocks/get the instructions name/dump the instruction. My main interest in developing this was to be able to gather statistics about LLVM IR using python scripts to speed up statistical profiling of different IR level transformations (hence the focus on printing/dumping/getting names). This is a gift from me to the LLVM community = ). I am going to be committing the patches slowly over the next bit as I have time to prepare the patches. The overall organization follows the c-api like the bindings that are already implemented. llvm-svn: 190388
2013-05-07We're in 3.4 land now.Bill Wendling1-1/+1
llvm-svn: 181350
2012-12-01[python] Add markup option to disassemblerGregory Szorc2-1/+23
Patch contributed by Wladimir J. van der Laan <laanwj@gmail.com> llvm-svn: 169102
2012-11-20[python] fix get_library()Anders Waldenborg1-15/+35
Before this fix, the LLVM Python bindings on SVN trunk always fail with: Exception: LLVM shared library not found! since it's still looking for a library named "LLVM-3.1svn". Besides updating the LLVM version in the library name, this patch also changes llvm.get_library() to make it possible to run the unit tests without installing the LLVM shared library into a default linker search path. e.g. after this patch, running the llvm/python unit tests with: LD_LIBRARY_PATH=../build/Debug+Asserts/lib nosetests -v bindings/python/llvm/tests/ would work on Linux. Patch from Scott Tsai (with some minor modifications) Patch also acked by Gregory Szorc llvm-svn: 168390
2012-03-22[python] Add negative MemoryBuffer testcaseAnders Waldenborg1-0/+5
llvm-svn: 153248
2012-03-21[python] Add some paths where to find test binaryAnders Waldenborg1-0/+2
Adds /usr/lib/debug early to list, as some systems (debian) have unstripped libs in there Adds /lib/i386-linux-gnu for systems that does multiarch (debian) llvm-svn: 153174
2012-03-21[python] Mark get_test_binary as not being a testAnders Waldenborg1-0/+1
get_test_binary is a helper method, not a test, make sure nosetests doesn't pick it up as a test. llvm-svn: 153173
2012-03-11[llvm.py] Implement disassembler interfaceGregory Szorc2-0/+162
It doesn't currently support the op info and symbol lookup callbacks, but it is better than nothing. llvm-svn: 152527
2012-03-10Revert "[llvm.py] Implement interface to enhanced disassembler"Gregory Szorc2-626/+0
Chris Lattner says the edis interface is going away. It doesn't make sense to land something that will go away in the near future. llvm-svn: 152508
2012-03-10[llvm.py] Implement interface to enhanced disassemblerGregory Szorc2-0/+626
This requires a C++ change to EDDisassembler's ctor to function properly (the llvm::InitializeAll* functions aren't being called currently and there is no way to call them from Python). Code is partially tested and works well enough for initial commit. There are probably many small bugs. llvm-svn: 152506
2012-03-10[llvm.py] Make LLVMObject.__del__ work if called during __init__Gregory Szorc1-0/+3
llvm-svn: 152505
2012-03-10[llvm.py] Define enumerations from Core.h; add OpCode classGregory Szorc3-2/+265
llvm-svn: 152483
2012-03-10[llvm.py] Implement interface to object filesGregory Szorc10-144/+620
It is now possible to load object files and scan over sections, symbols, and relocations! Includes test code with partial coverage. llvm-svn: 152482
2012-03-09[llvm.py] Make ObjectFile destructor workGregory Szorc3-17/+33
Previous code had a double free in MemoryBuffer. The tests now pass. llvm-svn: 152422
2012-03-09[llvm.py] Initial skeleton for Python LLVM bindingsGregory Szorc7-0/+361
This contains a semi-functional skeleton for the implementation of the LLVM bindings for Python. The API for the Object.h interface is roughly designed but not implemented. MemoryBufferRef is implemented and actually appears to work! The ObjectFile unit test fails with a segmentation fault because the LLVM library isn't being properly initialized. The build system doesn't know about this code yet, so no alerts should fire. llvm-svn: 152397
generated by cgit v1.1 at 2025-10-18 08:32:23 +0000