Displaying 4 results from an estimated 4 matches for "testgenasmmatch".
Did you mean:
testgenasmmatcher
2015 Aug 20
2
Problem Compiling AsmParser
...following lines to AsmParser/CMakeLists.txt (From the Assembler
Guide by Simon Cook from Embecosm Link
<http://www.embecosm.com/appnotes/ean10/ean10-howto-llvmas-1.0.pdf>)
*add_llvm_library(LLVMTestAsmParser TestAsmParser.cpp )*
and the followings to main CMakeLists.txt
*tablegen(LLVM TestGenAsmMatcher.inc
-gen-asm-matcher)add_subdirectory(AsmParser)*
Any help is appreciated.
Cheers,
ES
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150820/0a76e730/attachment.html>
2015 Sep 17
2
Register Number
...file, I defined a register like this:
class TestReg<bits<6> enc, string name> : Register<name> {
let HWEncoding{5-0} = enc;
let Namespace = "TEST";
}
def D0 : TestReg<0x01, "d0">, DwarfRegNum<[1]>;
but when I compile, the result I have in TestGenAsmMatcher.inc is this:
case 'd': // 7 strings to match.
switch (Name[1]) {
case '0': // 1 string to match.
return* 14*; // "d0"
I supposed I will get either 1 (because of encoding) or 0 (because of
DwarfRegNum). Is this 14 something system generated? Ho...
2015 Sep 17
2
Register Number
On 9/17/2015 7:04 AM, Sky Flyer via llvm-dev wrote:
> It seems like d0 is always 14!
> I check it with ARMGenAsmMatcher.inc it was the same!
> How is it possible? because it should give the same register value that
> matches the underlying platform not any autogenerated value!?
The returned number is the register id as defined in
<YourTarget>GenRegisterInfo.inc. These numbers
2015 Sep 17
2
Register Number
...<0x01, "d0">, DwarfRegNum<[0]>;*
>
> and then in InstInfo.td
> *bits<6> Dr;
> let Inst{5-3} = Dr{2-0};*
>
> assuming D0 is passed to $Dr, what I get in the encoding is 110, which I
> think is the bit 0 to 2 of what is the returned value in the
> TestGenAsmMatcher.inc.
> I mean, at the end, Inst{5-3} is getting a value which is not 001.
> What am I doing wrong?
>
I'm assuming that your TestReg definition assigns the 0x01 to the
HWEncoding field.
In an instruction definition, the way that tablegen assigns values from
the parameters is that...