Displaying 6 results from an estimated 6 matches for "armoperand".
2010 Jun 21
2
[LLVMdev] MC: Object file specific parsing
...arser() const { return Parser; }
-
- MCAsmLexer &getLexer() const { return Parser.getLexer(); }
-
- void Warning(SMLoc L, const Twine &Msg) { Parser.Warning(L, Msg); }
-
- bool Error(SMLoc L, const Twine &Msg) { return Parser.Error(L, Msg); }
-
bool MaybeParseRegister(OwningPtr<ARMOperand> &Op, bool ParseWriteBack);
bool ParseRegisterList(OwningPtr<ARMOperand> &Op);
@@ -81,8 +72,8 @@ private:
/// @name Auto-generated Match Functions
/// {
- bool MatchInstruction(const SmallVectorImpl<MCParsedAsmOperand*> &Operands,
- MC...
2012 Oct 17
3
[LLVMdev] Hexagon Assembly parser question
...LVM assembly parser. It seem like there
is a lot of work that has been done to make this parsing straightforward.
But..
Hexagon assembly does not follow the "Mnemonic Rx Rx ." format that is
expected by the assembly parsing infrastructure, represented by:
StringRef Mnemonic = ((ARMOperand*)Operands[0])->getToken();
This Mnemonic location assumption applies to both the Tablegen Backend
AsmMatcherEmitter processing, and the .inc file it produces where
MatchInstructionImpl is the entry point by which the assembly input is
parsed.
However Hexagon assembly has some features...
2010 May 05
0
[LLVMdev] Is the option --enable-shared discontinued in 2.7?
...e)::ARMAsmParser::MatchRegisterName(llvm::StringRef const&)':
: undefined reference to `memcmp'
/tmp/llvm-build/2.7/llvm-objects/Release/lib/libLLVMARMAsmParser.a(ARMAsmParser.o)(.text+0xdd5):
In function `(anonymous
namespace)::ARMAsmParser::MaybeParseRegister((anonymous
namespace)::ARMOperand&, bool)':
: undefined reference to `__assert'
Linking command line was:
/usr/local/gcc/4.5.0/bin/g++ -I/tmp/llvm-build/2.7/llvm-objects/include
-I/tmp/llvm-build/2.7/llvm-objects/tools/llvm-shlib
-I/tmp/llvm-build/2.7/llvm/include
-I/tmp/llvm-build/2.7/llvm/tools/llvm-shlib -D_DEBU...
2010 May 04
3
[LLVMdev] Is the option --enable-shared discontinued in 2.7?
On Thu, Apr 29, 2010 at 6:31 PM, Jeffrey Yasskin <jyasskin at google.com> wrote:
> On Wed, Apr 28, 2010 at 10:48 AM, Yuri <yuri at tsoft.com> wrote:
>> Jeffrey Yasskin wrote:
>>>
>>> We currently use two different techniques to get whole libraries
>>> included into the .so. On Linux (gnu ld and gold), we pass
>>> --whole-archive, while on
2012 Oct 17
0
[LLVMdev] Hexagon Assembly parser question
...assembly parser. It seem like there is a lot of work that has been done to make this parsing straightforward.
>
> But….
> Hexagon assembly does not follow the “Mnemonic Rx Rx …” format that is expected by the assembly parsing infrastructure, represented by:
> StringRef Mnemonic = ((ARMOperand*)Operands[0])->getToken();
>
> This Mnemonic location assumption applies to both the Tablegen Backend AsmMatcherEmitter processing, and the .inc file it produces where MatchInstructionImpl is the entry point by which the assembly input is parsed.
>
> However Hexagon assembly has...
2010 May 05
2
[LLVMdev] Is the option --enable-shared discontinued in 2.7?
...hRegisterName(llvm::StringRef const&)':
> : undefined reference to `memcmp'
> /tmp/llvm-build/2.7/llvm-objects/Release/lib/libLLVMARMAsmParser.a(ARMAsmParser.o)(.text+0xdd5):
> In function `(anonymous
> namespace)::ARMAsmParser::MaybeParseRegister((anonymous
> namespace)::ARMOperand&, bool)':
> : undefined reference to `__assert'
>
> Linking command line was:
> /usr/local/gcc/4.5.0/bin/g++ -I/tmp/llvm-build/2.7/llvm-objects/include
> -I/tmp/llvm-build/2.7/llvm-objects/tools/llvm-shlib
> -I/tmp/llvm-build/2.7/llvm/include
> -I/tmp/llvm-build/2.7...