search for: object_format

.... > > > > 1. Define the target triple as follows (adapted from Triple.h): > > > > /// Target triples are strings in the canonical form: > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT > > > > 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object formats. &...

...or absence while parsing or normalizing. So here’s what I would suggest. 1. Define the target triple as follows (adapted from Triple.h): /// Target triples are strings in the canonical form: /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object formats. 3. Remove “MachO” from the llvm::Triple::EnvironmentTyp...

...**1. **Define the target triple as follows (adapted from Triple.h):* > *** > > ** ** > > /// Target triples are strings in the canonical form:**** > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM**** > > /// or**** > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT **** > > /// or**** > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT**** > > /// or**** > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT**** > > ** ** > > **2. **Add an llvm::Triple::ObjectFormatType enum with all > llvm...

...or absence while parsing or normalizing. So here’s what I would suggest. 1. Define the target triple as follows (adapted from Triple.h): /// Target triples are strings in the canonical form: /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object formats. 3. Remove “MachO” from the llvm::Triple::EnvironmentTyp...

...or absence while parsing or normalizing. So here’s what I would suggest. 1. Define the target triple as follows (adapted from Triple.h): /// Target triples are strings in the canonical form: /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object formats. 3. Remove “MachO” from the llvm::Triple::EnvironmentTyp...

...ould suggest. > > 1. Define the target triple as follows (adapted from Triple.h): > > > > /// Target triples are strings in the canonical form: > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT > > > > 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object formats. &...

...e the target triple as follows (adapted from Triple.h): >> >> >> >> /// Target triples are strings in the canonical form: >> >> /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM >> >> /// or >> >> /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT >> >> /// or >> >> /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT >> >> /// or >> >> /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT >> >> >> >> 2. Add an llvm::Triple::ObjectFormatTyp...

On Wed, Jul 25, 2012 at 12:24 AM, Kaylor, Andrew <andrew.kaylor at intel.com>wrote: > > -------------------------------**** > > ELF Support on Windows**** > > -------------------------------**** > > **** > > There are various reasons that it would be nice to be able to support > generation of ELF objects on Windows through the MCJIT interface, one of >

...or absence while parsing or normalizing. So here’s what I would suggest. 1. Define the target triple as follows (adapted from Triple.h): /// Target triples are strings in the canonical form: /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object formats. 3. Remove “MachO” from the llvm::Triple::EnvironmentTyp...

Following up and expanding on an earlier conversation, I'd like to discuss making several non-trivial changes to the MCJIT engine and related objects. There may be some interdependencies between these changes, but I think that they can be logically grouped as follows: * Lazy module compilation * Enhance the JIT memory manager interface to enable section-based memory protection * Clean up