search for: x86genasmmatcher

...`anonymous-namespace'::MatchEntry *, _Ty=llvm::StringRef, _Iter=const `anonymous-namespace'::MatchEntry *, _Pr=`anonymous-namespace'::LessOpcode, _Diff=std::iterator_traits::difference_type ] C:\dev\src\llvm\lib\Target\X86\X86GenAsmMatcher.inc(4583) : see reference to function template instantiation 'std::pair<_Ty1,_Ty2> std::equal_range(_FwdIt,_FwdIt,const _Ty &,_Pr)' being compiled with [ _Ty1=const `anonymous-namespace'::MatchEntry *, _Ty2=const `anonymous-namespace'...

...lvm-mc.exe -x86-asm-syntax=intel test_bad.s -o - test_bad.s:1:1: error: invalid operand for instruction mov eax, flags ^ .text After investigation, I saw that the memory location named "flags" was matched to the EFLAGS register in the MatchRegisterName() function in the generated X86GenAsmMatcher.inc. case 'f': // 1 string to match. if (memcmp(Name.data()+1, "lags", 4)) break; return 25; // "flags" So basically, what I'm seeing with "flags" (which should be a legit variable name) is that the X86AsmParser creates a referenc...

...src\llvm-build\lib\Target\X86\X86CommonTableGen.vcxproj" (38) auf Knoten "1" (Standardziele). InitializeBuildStatus: "x64\Debug\X86CommonTableGen\X86Commo.1917F16D.tlog\unsuccessfulbuild" wird erstellt, da "AlwaysCreate" angegeben wurde. CustomBuild:   Building X86GenAsmMatcher.inc...   Building X86GenAsmWriter.inc...   Building X86GenAsmWriter1.inc...   Building X86GenCallingConv.inc...   Building X86GenDAGISel.inc...   Building X86GenDisassemblerTables.inc...   Building X86GenEVEX2VEXTables.inc...   Building X86GenFastISel.inc...   Building X86GenGlobalISel.inc....

...test_bad.s:1:1: error: invalid operand for instruction > > mov eax, flags > > ^ > > .text > > > > After investigation, I saw that the memory location named “flags” was > matched to the EFLAGS register in the MatchRegisterName() function in the > generated X86GenAsmMatcher.inc. > > > > case 'f': // 1 string to match. > > if (memcmp(Name.data()+1, "lags", 4)) > > break; > > return 25; // "flags" > > > > So basically, what I’m seeing with “flags” (which should be a legit >...

...lags >llvm-mc.exe -x86-asm-syntax=intel test_bad.s -o - test_bad.s:1:1: error: invalid operand for instruction mov eax, flags ^ .text After investigation, I saw that the memory location named “flags” was matched to the EFLAGS register in the MatchRegisterName() function in the generated X86GenAsmMatcher.inc. case 'f': // 1 string to match. if (memcmp(Name.data()+1, "lags", 4)) break; return 25; // "flags" So basically, what I’m seeing with “flags” (which should be a legit variable name) is that the X86AsmParser creates a reference to an implic...

...9;::MatchEntry *, > _Ty=llvm::StringRef, > _Iter=const `anonymous-namespace'::MatchEntry *, > _Pr=`anonymous-namespace'::LessOpcode, > _Diff=std::iterator_traits::difference_type > ] > C:\dev\src\llvm\lib\Target\X86\X86GenAsmMatcher.inc(4583) : > see reference to function template instantiation 'std::pair<_Ty1,_Ty2> > std::equal_range(_FwdIt,_FwdIt,const _Ty &,_Pr)' being compiled > with > [ > _Ty1=const `anonymous-namespace'::MatchEntry *, > _Ty2=cons...

...test_bad.s:1:1: error: invalid operand for instruction > > mov eax, flags > > ^ > > .text > > > > After investigation, I saw that the memory location named “flags” was > matched to the EFLAGS register in the MatchRegisterName() function in the > generated X86GenAsmMatcher.inc. > > > > case 'f': // 1 string to match. > > if (memcmp(Name.data()+1, "lags", 4)) > > break; > > return 25; // "flags" > > > > So basically, what I’m seeing with “flags” (which should be a legit >...

...t; test_bad.s:1:1: error: invalid operand for instruction > > mov eax, flags > > ^ > > .text > > > > After investigation, I saw that the memory location named “flags” was matched to the EFLAGS register in the MatchRegisterName() function in the generated X86GenAsmMatcher.inc. > > > > case 'f': // 1 string to match. > > if (memcmp(Name.data()+1, "lags", 4)) > > break; > > return 25; // "flags" > > > > So basically, what I’m seeing with “flags” (which should be a...

..._Ty=llvm::StringRef, > > _Iter=const `anonymous-namespace'::MatchEntry *, > > _Pr=`anonymous-namespace'::LessOpcode, > > _Diff=std::iterator_traits::difference_type > > ] > > C:\dev\src\llvm\lib\Target\X86\X86GenAsmMatcher.inc(4583) : > > see reference to function template instantiation 'std::pair<_Ty1,_Ty2> > > std::equal_range(_FwdIt,_FwdIt,const _Ty &,_Pr)' being compiled > > with > > [ > > _Ty1=const `anonymous-namespace'::MatchEntry *,...

...nc +SparcGenCallingConv.inc +SparcGenDAGISel.inc +SparcGenInstrInfo.inc +SparcGenRegisterInfo.inc +SparcGenSubtargetInfo.inc diff --git a/lib/Target/X86/.gitignore b/lib/Target/X86/.gitignore new file mode 100644 index 0000000..13e4a62 --- /dev/null +++ b/lib/Target/X86/.gitignore @@ -0,0 +1,11 @@ +X86GenAsmMatcher.inc +X86GenAsmWriter.inc +X86GenAsmWriter1.inc +X86GenCallingConv.inc +X86GenDAGISel.inc +X86GenDisassemblerTables.inc +X86GenEDInfo.inc +X86GenFastISel.inc +X86GenInstrInfo.inc +X86GenRegisterInfo.inc +X86GenSubtargetInfo.inc diff --git a/lib/Target/XCore/.gitignore b/lib/Target/XCore/.gitignore n...

my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) x64 Native Tools Command Prompt for VS 2017 directory structure: test     llvm <-- git clone https://github.com/llvm-mirror/llvm, git checkout release_70       tools         clang <-- git clone https://github.com/llvm-mirror/clang, git checkout