Displaying 5 results from an estimated 5 matches for "ad_att".
2014 Jan 29
6
[LLVMdev] making emitInlineAsm protected
I would like to make the following member of AsmPrinter be protected
void EmitInlineAsm(StringRef Str, const MDNode *LocMDNode = 0,
InlineAsm::AsmDialect AsmDialect =
InlineAsm::AD_ATT) const;
I have some stubs that I want to emit in MipsAsmParser .
Are there any objections to doing this?
Reed
2014 Jan 29
3
[LLVMdev] making emitInlineAsm protected
....com> wrote:
>> I would like to make the following member of AsmPrinter be protected
>>
>>
>> void EmitInlineAsm(StringRef Str, const MDNode *LocMDNode = 0,
>> InlineAsm::AsmDialect AsmDialect =
>> InlineAsm::AD_ATT) const;
>>
>> I have some stubs that I want to emit in MipsAsmParser .
>>
>> Are there any objections to doing this?
>>
>> Reed
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu...
2014 Jan 31
4
[LLVMdev] making emitInlineAsm protected
...> wrote:
> > I would like to make the following member of AsmPrinter be protected
> >
> >
> > void EmitInlineAsm(StringRef Str, const MDNode *LocMDNode = 0,
> > InlineAsm::AsmDialect AsmDialect =
> > InlineAsm::AD_ATT) const;
> >
> > I have some stubs that I want to emit in MipsAsmParser .
>
> You mean Printer? There is no such a thing as inline asm in a .s file.
>
> > Are there any objections to doing this?
>
> Probably. EmitInilneAsm is the only case I know that has a reason...
2014 Jan 29
6
[LLVMdev] making emitInlineAsm protected
....com> wrote:
>> I would like to make the following member of AsmPrinter be protected
>>
>>
>> void EmitInlineAsm(StringRef Str, const MDNode *LocMDNode = 0,
>> InlineAsm::AsmDialect AsmDialect =
>> InlineAsm::AD_ATT) const;
>>
>> I have some stubs that I want to emit in MipsAsmParser .
> You mean Printer? There is no such a thing as inline asm in a .s file.
>
>> Are there any objections to doing this?
> Probably. EmitInilneAsm is the only case I know that has a reasonable
> use of...
2016 Jun 13
2
LLVM IR intrinsics placeholder for strings [was Re: Back end with special loop instructions (using LLVM IR intrinsics)]
Hello.
I come back to this thread. But I want to ask a slightly different question.
Is there a way to have LLVM IR language intrinsics that are given at construction
time a string that is written at assembly generation time as it is? (so, basically having
placeholders of strings in LLVM that remain untouched until the end, including code
generation time.)
More exactly, I would