Displaying 5 results from an estimated 5 matches for "lessopcode".
2010 Sep 07
3
[LLVMdev] MS VS2008 build fails - X86AsmParser
...I see a few commits from yesterday that may have something to do with it, but no
idea what the solution is.
-David
See MSVC's beautiful and concise output below;
Compiling...
X86AsmParser.cpp
C:\dev\MSVisualStudio\VC\include\xutility(313) : error C2664: 'bool
`anonymous-namespace'::LessOpcode::operator ()(llvm::StringRef,const
`anonymous-namespace'::MatchEntry &)' : cannot convert parameter 1
from 'const `anonymous-namespace'::MatchEntry' to 'llvm::StringRef'
No user-defined-conversion operator available that can perform
this conversion, or the op...
2010 Sep 07
0
[LLVMdev] MS VS2008 build fails - X86AsmParser
...ion is.
Wow, that's a pretty terrible diagnostic. Does r113198 help?
-Chris
>
> See MSVC's beautiful and concise output below;
>
> Compiling...
> X86AsmParser.cpp
> C:\dev\MSVisualStudio\VC\include\xutility(313) : error C2664: 'bool
> `anonymous-namespace'::LessOpcode::operator ()(llvm::StringRef,const
> `anonymous-namespace'::MatchEntry &)' : cannot convert parameter 1
> from 'const `anonymous-namespace'::MatchEntry' to 'llvm::StringRef'
> No user-defined-conversion operator available that can perform
> this co...
2011 Mar 09
0
[LLVMdev] Unable to build latest with Visual Studio 2008
...le diagnostic. Does r113198 help?
>
> -Chris
>
> > See MSVC's beautiful and concise output below;
> >
> > Compiling...
> > X86AsmParser.cpp
> > C:\dev\MSVisualStudio\VC\include\xutility(313) : error C2664: 'bool
> > `anonymous-namespace'::LessOpcode::operator ()(llvm::StringRef,const
> > `anonymous-namespace'::MatchEntry &)' : cannot convert parameter 1
> > from 'const `anonymous-namespace'::MatchEntry' to 'llvm::StringRef'
> > No user-defined-conversion operator available that can perfo...
2012 May 22
2
[LLVMdev] Match operands
...32, MCK_FGR32 }, 0, 0},
.
.
.
}
So, when the MatchInstructionImpl is called it seems to look for a pair of instructions that match the mnemonic:
// Search the table.
std::pair<const MatchEntry*, const MatchEntry*> MnemonicRange =
std::equal_range(MatchTable, MatchTable+277, Mnemonic, LessOpcode());
The search will always end in first two entries ( Mips::CEIL_L_D64 and Mips::CEIL_L_S) thus reporting the 'invalid operand' error when ceil.w.x instruction is parsed.
Is there a way to direct this search somehow, maybe to use available features or we should change the definition of the...
2012 May 22
0
[LLVMdev] Match operands
...}
>
> So, when the MatchInstructionImpl is called it seems to look for a pair of instructions that match the mnemonic:
>
> // Search the table.
> std::pair<const MatchEntry*, const MatchEntry*> MnemonicRange =
> std::equal_range(MatchTable, MatchTable+277, Mnemonic, LessOpcode());
>
> The search will always end in first two entries ( Mips::CEIL_L_D64 and Mips::CEIL_L_S) thus reporting the 'invalid operand' error when ceil.w.x instruction is parsed.
> Is there a way to direct this search somehow, maybe to use available features or we should change the de...