Displaying 6 results from an estimated 6 matches for "doesallowquotesinnam".
Did you mean:
doesallowquotesinname
2012 Oct 02
2
[LLVMdev] [patch] set AssemblerDialect
...7e 100644
--- a/include/llvm/MC/MCAsmInfo.h
+++ b/include/llvm/MC/MCAsmInfo.h
@@ -453,6 +453,9 @@ namespace llvm {
unsigned getAssemblerDialect() const {
return AssemblerDialect;
}
+ void setAssemblerDialect(unsigned dialect) {
+ AssemblerDialect = dialect;
+ }
bool doesAllowQuotesInName() const {
return AllowQuotesInName;
}
2012 Oct 02
0
[LLVMdev] [patch] set AssemblerDialect
....h
> +++ b/include/llvm/MC/MCAsmInfo.h
> @@ -453,6 +453,9 @@ namespace llvm {
> unsigned getAssemblerDialect() const {
> return AssemblerDialect;
> }
> + void setAssemblerDialect(unsigned dialect) {
> + AssemblerDialect = dialect;
> + }
> bool doesAllowQuotesInName() const {
> return AllowQuotesInName;
> }
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
2012 Oct 03
1
[LLVMdev] [patch] set AssemblerDialect
...AsmInfo.h
>> @@ -453,6 +453,9 @@ namespace llvm {
>> unsigned getAssemblerDialect() const {
>> return AssemblerDialect;
>> }
>> + void setAssemblerDialect(unsigned dialect) {
>> + AssemblerDialect = dialect;
>> + }
>> bool doesAllowQuotesInName() const {
>> return AllowQuotesInName;
>> }
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...robably because the Darwin assembler supports quoted symbols (i.e. you can enclose an identifier in quotes). Maybe Joe is right, and you should change the LLVM mangler to not mangle '?' chars (if the assembler can handle it). Or maybe we should see if GAS supports quoted symbols (MCAsmInfo::doesAllowQuotesInName()).
Chip
>
> Sent from my iPhone
>
> On Nov 25, 2011, at 2:15 PM, Charles Davis <cdavis at mymail.mines.edu> wrote:
>
>>
>> On Nov 25, 2011, at 8:39 AM, Michael Spencer wrote:
>>
>>> So I was taking a look at Microsoft C++ ABI support while on...
2011 Nov 25
2
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it.
Sent from my iPhone
On Nov 25, 2011, at 2:15 PM, Charles Davis <cdavis at mymail.mines.edu> wrote:
>
> On Nov 25, 2011, at 8:39 AM, Michael Spencer wrote:
>
>> So I was taking a look at Microsoft C++ ABI support while on vacation,
>> and ran into a major
2011 Nov 26
1
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...robably because the Darwin assembler supports quoted symbols (i.e. you can enclose an identifier in quotes). Maybe Joe is right, and you should change the LLVM mangler to not mangle '?' chars (if the assembler can handle it). Or maybe we should see if GAS supports quoted symbols (MCAsmInfo::doesAllowQuotesInName()).
>
> Chip
So setting AllowQuotesInName=true gets the correct names in the
output. However, it breaks MinGW. The issue is of course that
MCAsmInfo mixes both assembler and object file format capabilities.
Allowing quoted names has nothing to do with COFF ;/. So it seems we
need a new AsmI...