Displaying 9 results from an estimated 9 matches for "createmcasmparser".
2012 May 09
0
[LLVMdev] JIT support for inline asm on Linux
Resending, any pointers are much appreciated.
On 5/7/2012 11:16 PM, Ashok Nalkund wrote:
>
>
> On 5/7/2012 10:17 PM, Bendersky, Eli wrote:
> <snip>
>>>> $lli -entry-function="ISimEngine_GetVersion" -use-mcjit libengine.bc
>>>> LLVM ERROR: Inline asm not supported by this streamer because we don't
>>>> have an asm parser for this
2012 May 08
2
[LLVMdev] JIT support for inline asm on Linux
On 5/7/2012 10:17 PM, Bendersky, Eli wrote:
<snip>
>>> $lli -entry-function="ISimEngine_GetVersion" -use-mcjit libengine.bc
>>> LLVM ERROR: Inline asm not supported by this streamer because we don't
>>> have an asm parser for this target
>>
>> I also tried other variations of the call with the same result:
>>> $lli
2015 Sep 23
2
The Trouble with Triples
...4 objects. This information comes from MipsAsmBackend and ultimately comes from Triple::mips/mipsel vs Triple::mips64/mips64el. This is incorrect for N32 (which should be ELF32 but has Triple::mips64/mips64el) and for mips-linux-gnu –mips64 (which should be ELF32 since it should target O32).
* Call createMCAsmParser()
* Call a different createMCAsmParser().
Other places that get ABI information wrong:
* AddressSanitizer: Uses Triple::mips64/mips64el to mean the N64 ABI. N32 is a Triple::mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
* DataFlowSanitizer: Is heading down the same road b...
2015 Sep 23
2
The Trouble with Triples
...4 objects. This information comes from MipsAsmBackend and ultimately comes from Triple::mips/mipsel vs Triple::mips64/mips64el. This is incorrect for N32 (which should be ELF32 but has Triple::mips64/mips64el) and for mips-linux-gnu –mips64 (which should be ELF32 since it should target O32).
* Call createMCAsmParser()
* Call a different createMCAsmParser().
Other places that get ABI information wrong:
* AddressSanitizer: Uses Triple::mips64/mips64el to mean the N64 ABI. N32 is a Triple::mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
* DataFlowSanitizer: Is heading down the same road...
2015 Sep 23
4
The Trouble with Triples
...4 objects. This information comes from MipsAsmBackend and ultimately comes from Triple::mips/mipsel vs Triple::mips64/mips64el. This is incorrect for N32 (which should be ELF32 but has Triple::mips64/mips64el) and for mips-linux-gnu –mips64 (which should be ELF32 since it should target O32).
* Call createMCAsmParser()
* Call a different createMCAsmParser().
Other places that get ABI information wrong:
* AddressSanitizer: Uses Triple::mips64/mips64el to mean the N64 ABI. N32 is a Triple::mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
* DataFlowSanitizer: Is heading down the same road...
2015 Sep 24
3
The Trouble with Triples
...4 objects. This information comes from MipsAsmBackend and ultimately comes from Triple::mips/mipsel vs Triple::mips64/mips64el. This is incorrect for N32 (which should be ELF32 but has Triple::mips64/mips64el) and for mips-linux-gnu –mips64 (which should be ELF32 since it should target O32).
* Call createMCAsmParser()
* Call a different createMCAsmParser().
Other places that get ABI information wrong:
* AddressSanitizer: Uses Triple::mips64/mips64el to mean the N64 ABI. N32 is a Triple::mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
* DataFlowSanitizer: Is heading down the same road...
2015 Sep 23
4
The Trouble with Triples
...formation comes from MipsAsmBackend and ultimately comes from Triple::mips/mipsel vs Triple::mips64/mips64el. This is incorrect for N32 (which should be ELF32 but has Triple::mips64/mips64el) and for mips-linux-gnu –mips64 (which should be ELF32 since it should target O32).
· If assembling createMCAsmParser
· If disassembling:
o createMCRegInfo() (again)
o createMCAsmInfo() (again)
§ This has the same issues as the first call.
o createMCDisassembler()
Clang does pretty much the same thing as this but additionally has to deal with using the correct default ABI for the given triple....
2015 Sep 23
3
The Trouble with Triples
...formation comes from MipsAsmBackend and ultimately comes from Triple::mips/mipsel vs Triple::mips64/mips64el. This is incorrect for N32 (which should be ELF32 but has Triple::mips64/mips64el) and for mips-linux-gnu –mips64 (which should be ELF32 since it should target O32).
• If assembling createMCAsmParser
• If disassembling:
o createMCRegInfo() (again)
o createMCAsmInfo() (again)
• This has the same issues as the first call.
o createMCDisassembler()
Clang does pretty much the same thing as this but additionally has to deal with using the correct default ABI for the given triple....
2015 Sep 22
2
The Trouble with Triples
>> Here's the line of thought that I'd like people to start with:
>> * Triples don't describe the target. They look like they should, but they
>> don't. They're really just arbitrary strings.
>
>Triples are used as a starting point, but no more.
I disagree with this but for now let's assume it's true. The starting point is
incorrect because