search for: printfatalerror

Displaying 6 results from an estimated 6 matches for "printfatalerror".

2017 Dec 15
2
InstAlias with tied operands - can it be supported?
Hello, InstAlias does not allow tied operands (repeated operands) in the asm string to be matched. It seems this situation is explicitly prevented in AsmMatcherEmitter.cpp: if (!Hack) PrintFatalError(TheDef->getLoc(), "ERROR: matchable with tied operand '" + Tok + "' can never be matched!"); // FIXME: Should reject these. The ARM backend hits this with $lane in a // bunch of instructions. It is unc...
2016 Jul 15
2
TableGen change in LLVM 3.9 allows only prefix instruction notation
...ble for this from llvm/utils/TableGen/AsmMatcherEmitter.cpp (so it needs to be commented to be disabled): // The first token of the instruction is the mnemonic, which must be a // simple string, not a $foo variable or a singleton register. if (AsmOperands.empty()) PrintFatalError(TheDef->getLoc(), "Instruction '" + TheDef->getName() + "' has no tokens"); assert(!AsmOperands[0].Token.empty()); if (HasMnemonicFirst) { Mnemonic = AsmOperands[0].Token; if (Mnemonic[0] == '$')...
2020 Sep 08
2
TableGen enhancements
...ing with TableGen in order to improve the ability of backends to generate error messages with more precise source locations. The main requirement was to add a slot to the RecordVal class to hold the source location of the statement that defined the field. To make that easier to use, I added a third PrintFatalError() method that accepts a RecordVal and grabs the source location from it. To test these ideas, I worked on the SearchableTable backend. It now includes in every message at least the record location and often the field definition location. I also reworded some message to make them more consistent....
2017 Dec 15
0
InstAlias with tied operands - can it be supported?
..., via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello, > > InstAlias does not allow tied operands (repeated operands) in the asm string to be matched. > > It seems this situation is explicitly prevented in AsmMatcherEmitter.cpp: > > if (!Hack) > PrintFatalError(TheDef->getLoc(), > "ERROR: matchable with tied operand '" + Tok + > "' can never be matched!"); > // FIXME: Should reject these. The ARM backend hits this with $lane in a > // bunch of instructions....
2018 Jan 04
1
InstAlias with tied operands - can it be supported?
...>> >> Hello, >> >> InstAlias does not allow tied operands (repeated operands) in the asm >> string to be matched. >> >> It seems this situation is explicitly prevented in >> AsmMatcherEmitter.cpp: >> >> if (!Hack) >> PrintFatalError(TheDef->getLoc(), >> "ERROR: matchable with tied operand '" + Tok + >> "' can never be matched!"); >> // FIXME: Should reject these. The ARM backend hits this with >> $lane in a >>...
2020 Jul 24
2
[RFC] Preferred error/note style across non-clang tools, e.g. tablegen
> On Jul 22, 2020, at 18:09, Jonathan Roelofs <jonathan_roelofs at apple.com> wrote: > > > >> On Jul 22, 2020, at 4:31 PM, Evandro Menezes <evandro.menezes at sifive.com <mailto:evandro.menezes at sifive.com>> wrote: >>> Sure, let’s talk about what that end goal should be! Can you give some other examples of where these inconsistencies could be