search for: lto_module_is_object_file

Displaying 4 results from an estimated 4 matches for "lto_module_is_object_file".

2008 Feb 23
5
[LLVMdev] new LTO C interface
...extern "C" { #endif // // returns a printable string // extern const char* lto_get_version(); // // returns the last error string or NULL if last operation was sucessful // extern const char* lto_get_error_message(); // // validates if a file is a loadable object file // extern bool lto_module_is_object_file(const char* path); // // validates if a file is a loadable object file compilable for requested target // extern bool lto_module_is_object_file_for_target(const char* path, const char* target_triplet_prefix); // // validates if a buffer is a load...
2015 Jun 03
4
[LLVMdev] Updated RFC: ThinLTO Implementation Plan
...he object file as bitcode or not, or how hard it is to pass the resulting object file along to the libLTO routines for handling (they automatically handle the native-wrapped object files so the linker shouldn't have to do anything special to read them). Specifically, in the C API these are the lto_module_is_object_file* variants, which will return true for either straight-up or native-wrapped bitcode. All of the mechanics of handling bitcode vs native object-wrapped bitcode are down in the IRObjectFile handling. So the LTOModule:isBitcode*/lto_module_is_object_file* will correctly identify native object-wrapped b...
2008 Feb 25
0
[LLVMdev] new LTO C interface
...st char* > lto_get_version(); > > > // > // returns the last error string or NULL if last operation was > sucessful > // > extern const char* > lto_get_error_message(); > > > // > // validates if a file is a loadable object file > // > extern bool > lto_module_is_object_file(const char* path); > > > // > // validates if a file is a loadable object file compilable for > requested target > // > extern bool > lto_module_is_object_file_for_target(const char* path, > const char* > target_triplet_p...
2015 May 29
4
[LLVMdev] Updated RFC: ThinLTO Implementation Plan
On Fri, May 29, 2015 at 6:56 AM, Alex Rosenberg <alexr at leftfield.org> wrote: > My earlier statement about wrapping things in a native object file held in that it is controversial. It appears to be still central to your design. > > It may help to look at the problem from a different viewpoint: LLVM is not a compiler. It is a framework that can be used to make compiler-like tools.