Displaying 12 results from an estimated 12 matches for "getobjectformat".
2012 Aug 17
3
[LLVMdev] RFC: MCJIT enhancements
...Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr)
>
> Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr, const Twine &EnvStr)
>
> bool hasExplicitObjectFormat() const
>
> ObjectFormatType getObjectFormat() const
>
> StringRef getObjectFormatName() const
>
> bool isOutputObjectFormatELF() const
>
> bool isOutputObjectFormatCOFF() const
>
> bool isOutputObjectFormatMachO() const
>
> static const char * getObjectFormatName(ObjectFormatType Kind)
>
>
>
&g...
2012 Aug 16
2
[LLVMdev] RFC: MCJIT enhancements
...onst Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr)
Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr, const Twine &EnvStr)
bool hasExplicitObjectFormat() const
ObjectFormatType getObjectFormat() const
StringRef getObjectFormatName() const
bool isOutputObjectFormatELF() const
bool isOutputObjectFormatCOFF() const
bool isOutputObjectFormatMachO() const
static const char * getObjectFormatName(ObjectFormatType Kind)
5. When an object format is specified, it will be used by MC a...
2012 Aug 17
0
[LLVMdev] RFC: MCJIT enhancements
...tr, const Twine &OSStr,
> const Twine &ObjFmtStr)****
>
> Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr,
> const Twine &ObjFmtStr, const Twine &EnvStr)****
>
> bool hasExplicitObjectFormat() const****
>
> ObjectFormatType getObjectFormat() const****
>
> StringRef getObjectFormatName() const****
>
> bool isOutputObjectFormatELF() const****
>
> bool isOutputObjectFormatCOFF() const****
>
> bool isOutputObjectFormatMachO() const****
>
> static const char * getObjectFormatName(ObjectFormatType Kind)****
&g...
2012 Sep 05
2
[LLVMdev] RFC: MCJIT enhancements
...onst Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr)
Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr, const Twine &EnvStr)
bool hasExplicitObjectFormat() const
ObjectFormatType getObjectFormat() const
StringRef getObjectFormatName() const
bool isOutputObjectFormatELF() const
bool isOutputObjectFormatCOFF() const
bool isOutputObjectFormatMachO() const
static const char * getObjectFormatName(ObjectFormatType Kind)
5. When an object format is specified, it will be used by MC a...
2012 Aug 28
0
[LLVMdev] RFC: MCJIT enhancements
...onst Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr)
Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr, const Twine &EnvStr)
bool hasExplicitObjectFormat() const
ObjectFormatType getObjectFormat() const
StringRef getObjectFormatName() const
bool isOutputObjectFormatELF() const
bool isOutputObjectFormatCOFF() const
bool isOutputObjectFormatMachO() const
static const char * getObjectFormatName(ObjectFormatType Kind)
5. When an object format is specified, it will be used by MC a...
2012 Sep 05
0
[LLVMdev] RFC: MCJIT enhancements
...Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr)
>
> Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr, const Twine &EnvStr)
>
> bool hasExplicitObjectFormat() const
>
> ObjectFormatType getObjectFormat() const
>
> StringRef getObjectFormatName() const
>
> bool isOutputObjectFormatELF() const
>
> bool isOutputObjectFormatCOFF() const
>
> bool isOutputObjectFormatMachO() const
>
> static const char * getObjectFormatName(ObjectFormatType Kind)
>
>
>
&g...
2012 Sep 07
2
[LLVMdev] RFC: MCJIT enhancements
...onst Twine &OSStr, const Twine &ObjFmtStr)
>>
>> Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr, const Twine &EnvStr)
>>
>> bool hasExplicitObjectFormat() const
>>
>> ObjectFormatType getObjectFormat() const
>>
>> StringRef getObjectFormatName() const
>>
>> bool isOutputObjectFormatELF() const
>>
>> bool isOutputObjectFormatCOFF() const
>>
>> bool isOutputObjectFormatMachO() const
>>
>> static const char * getObjectFormatName(Obje...
2014 Jun 19
2
[LLVMdev] [PATCH] triples for baremetal
...ackend is hardwired to assume AAPCS for M-class processors, ensure
// the frontend matches that.
if (Triple.getEnvironment() == llvm::Triple::EABI ||
- (Triple.getOS() == llvm::Triple::UnknownOS &&
+ (Triple.getOS() == llvm::Triple::NoneOS &&
Triple.getObjectFormat() == llvm::Triple::MachO) ||
StringRef(CPUName).startswith("cortex-m")) {
ABIName = "aapcs";
@@ -5128,7 +5128,7 @@
if (Str == "x86_64h")
T.setArchName(Str);
else if (Str == "armv6m" || Str == "armv7m" || Str == "armv7...
2012 Aug 16
0
[LLVMdev] RFC: MCJIT enhancements
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
>
2012 Sep 07
0
[LLVMdev] RFC: MCJIT enhancements
...onst Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr)
Triple(const Twine &ArchStr, const Twine &VendorStr, const Twine &OSStr, const Twine &ObjFmtStr, const Twine &EnvStr)
bool hasExplicitObjectFormat() const
ObjectFormatType getObjectFormat() const
StringRef getObjectFormatName() const
bool isOutputObjectFormatELF() const
bool isOutputObjectFormatCOFF() const
bool isOutputObjectFormatMachO() const
static const char * getObjectFormatName(ObjectFormatType Kind)
5. When an object format is specified, it will be used by MC a...
2014 Jun 17
4
[LLVMdev] triples for baremetal
[+llvmdev, -llvm-dev]
(Oopsies, llvmdev doesn't have a hyphen in it like all the others do)
On 6/17/14, 10:45 AM, Jonathan Roelofs wrote:
> [+llvm-dev, cfe-dev]
>
> Was "Re: [PATCH] ARM: allow inline atomics on Cortex M"
>
> On 6/17/14, 10:42 AM, Jonathan Roelofs wrote:
>>
>>
>> On 6/17/14, 9:35 AM, Renato Golin wrote:
>>> On 17 June 2014
2012 Jul 24
5
[LLVMdev] RFC: MCJIT enhancements
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