search for: xcoredisassembl

...e decoded as an ADD_3r instruction but instead it stops looking at this point and returns Fail. How should I deal with this situation? One idea I had (which I haven't tried yet) is to move the troublesome instructions into a different decoding table by setting the DecoderNamespace. This way in XCoreDisassembler::getInstruction() I can call decodeInstruction() on the first decoder table (containing INITSP_2r) and if this fails I can then call decodeInstruction() on the second decoder table (containing ADD_3r). Is this an abuse of DecoderNamespaces? Is there a better way of solving my problem? Thanks, R...

...as an ADD_3r instruction but instead it stops looking at this point and returns Fail. > > How should I deal with this situation? One idea I had (which I haven't tried yet) is to move the troublesome instructions into a different decoding table by setting the DecoderNamespace. This way in XCoreDisassembler::getInstruction() I can call decodeInstruction() on the first decoder table (containing INITSP_2r) and if this fails I can then call decodeInstruction() on the second decoder table (containing ADD_3r). Is this an abuse of DecoderNamespaces? Is there a better way of solving my problem? > >...

On Apr 8, 2013, at 2:55 PM, "Robinson, Paul" <Paul_Robinson at playstation.sony.com> wrote: I keep seeing "this is a layering violation" comments on the lists. > While there are a few llvm.org pages that mention layers in passing, > there is nothing (that I've found) actually specifying the layers. > Trying to infer the layering from the code is tedious and

I keep seeing "this is a layering violation" comments on the lists. While there are a few llvm.org pages that mention layers in passing, there is nothing (that I've found) actually specifying the layers. Trying to infer the layering from the code is tedious and error-prone (or we wouldn't see so many violations in code reviews, eh?). Now, I understand that Google has some sort

...e/build/./lib/Target/XCore/Release+Asserts/XCoreISelDAGToDAG.o differ: byte 22294, line 62 ./lib/Target/XCore/Release+Asserts/XCoreRegisterInfo.o ../../recurse2be/build/./lib/Target/XCore/Release+Asserts/XCoreRegisterInfo.o differ: byte 17460, line 12 ./lib/Target/XCore/Disassembler/Release+Asserts/XCoreDisassembler.o ../../recurse2be/build/./lib/Target/XCore/Disassembler/Release+Asserts/XCoreDisassembler.o differ: byte 119887, line 163 ./lib/Target/XCore/InstPrinter/Release+Asserts/XCoreInstPrinter.o ../../recurse2be/build/./lib/Target/XCore/InstPrinter/Release+Asserts/XCoreInstPrinter.o differ: byte 10736,...