[LLVMdev] assembler instruction selection vs. compiler instruction selection (original) (raw)
Steve King steve at metrokings.com
Fri Oct 3 14:16:09 PDT 2014
- Previous message: [LLVMdev] Weird problems with cos (was Re: [PATCH v3 2/3] R600: Add carry and borrow instructions. Use them to implement UADDO/USUBO)
- Next message: [LLVMdev] assembler instruction selection vs. compiler instruction selection
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello LLVM,
Suppose I have many instructions with AsmString "foo $src". The specific foo opcode depends on the value of $src. I arrange AsmOperandClasses and superclasses for $src so the assembler picks the right foo. That seems fine as far as the assembler goes.
During compiler instruction selection, I can use a CodeGenOnly=1 pseudo with assembly "foo $src" and emit .s files from llc. These go to the assembler which chooses the foo opcode using the AsmOperandClass hierarchy. The compiler didn't have to worry about which foo is the right foo.
However, I want to use llc's ability to produce object files directly. That path skips assembly parsing, so my AsmOperandClass logic can't help pick the right foo, correct?
What is the right approach? Do I add DAG pattern matching logic to mirror all the AsmOperandClass selection logic? If so, is there an easy way to detect if assembler instruction selection and compiler instruction selection are out of sync?
Thanks, -steve
- Previous message: [LLVMdev] Weird problems with cos (was Re: [PATCH v3 2/3] R600: Add carry and borrow instructions. Use them to implement UADDO/USUBO)
- Next message: [LLVMdev] assembler instruction selection vs. compiler instruction selection
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]