search for: objectformattyp

...> /// 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::EnvironmentType enum. > > 4. Add the following methods to llvm::Triple: > > > > Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, c...

...anonical 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::EnvironmentType enum. 4. Add the following methods to llvm::Triple: Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr) Triple(const...

...RE-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::EnvironmentType enum.** > ** > > **4. **Add the following methods to llvm::Triple:**** > > ** ** > > Triple(const Twine &ArchStr, const Twine &Vendo...

...anonical 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::EnvironmentType enum. 4. Add the following methods to llvm::Triple: Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr) Triple(const...

...anonical 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::EnvironmentType enum. 4. Add the following methods to llvm::Triple: Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr) Triple(const...

...> /// 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::EnvironmentType enum. > > 4. Add the following methods to llvm::Triple: > > > > Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, c...

...M-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::EnvironmentType enum. >> >> 4. Add the following methods to llvm::Triple: >> >> >> >> Triple(const Twine &ArchStr, const Twine &Vend...

Hi Jonathan, This looks a bit odd. Any reason for the unknown->none conflating in this way? For most (all) of the ports unknown-elf works the same as none-elf. I'm also not sure if someone decided to have, arm-codesourcery-elf that this would still work with the patch. Thoughts? -eric On Tue, Jun 24, 2014 at 7:35 AM, Amara Emerson <amara.emerson at gmail.com> wrote: > Hi Jon,

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 >

...anonical 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::EnvironmentType enum. 4. Add the following methods to llvm::Triple: Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr) Triple(const...

...RMSubArch_v5) - .EndsWith("v5t", Triple::ARMSubArch_v5) - .EndsWith("v5te", Triple::ARMSubArch_v5te) - .EndsWith("v4t", Triple::ARMSubArch_v4t) - .EndsWith("v4", Triple::ARMSubArch_v4) - .Default(Triple::NoSubArch); -} - static const char *getObjectFormatTypeName(Triple::ObjectFormatType Kind) { switch (Kind) { case Triple::UnknownObjectFormat: return ""; @@ -395,7 +381,6 @@ Triple::Triple(const Twine &Str) : Data(Str.str()), Arch(parseArch(getArchName())), - SubArch(parseSubArch(getArchName())), Vend...

> > The Triple object will remain unchanged. > > The Tuple will be the API to handle getting/setting parameters > depending on the Triple, compiler flags, attributes, etc. > > This part doesn't seem obvious from the direction the patches are going. > There will be no string representation of all options, as that would > be impossible, or at least, highly

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