search for: instructons

...alk about what comments you plan to add to these instructions? > Comments indicating what a memoperand are (for example) don't need to > be explicitly store in the machineinstr, they can be synthesized from > the MachineOperand directly. Some things we've used comments for: - Tag instructons with source line information (customers really want this). - Tag instructions as register spills or reloads. - Tag instructions as top-of-loop, with nesting information (we use this to do some static analysis on asm files). - Tag instructions with an ID of the tblgen pattern that generated the...

I am using llvm-project compiling risc-v programs. llvm-project version:dd8a2013dc1804be1b7d9cffacad2e984300bd22 Instructons to build LLVM+clang: ``` cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/home/llvm/workspace/llvm/llvm-project/llvm_install -DCMAKE_BUILD_TYPE="Release" -DDEFAULT_SYSROOT="/home/llvm/workspace/riscv/riscv-tc-20200220/bin/riscv32-unknown-elf" -DGCC_INSTALL_PREFIX="/home/llvm/workspa...

*llvm-project version:dd8a2013dc1804be1b7d9cffacad2e984300bd22* *Instructons to build LLVM+clang:* ``` cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/home/llvm/workspace/llvm/llvm-project/llvm_install -DCMAKE_BUILD_TYPE="Release" -DDEFAULT_SYSROOT="/home/llvm/workspace/riscv/riscv-tc-20200220/bin/riscv32-unknown-elf" -DGCC_INSTALL_PREFIX="/home/llvm/worksp...

...an to add to these instructions? >> Comments indicating what a memoperand are (for example) don't need to >> be explicitly store in the machineinstr, they can be synthesized from >> the MachineOperand directly. > > Some things we've used comments for: > > - Tag instructons with source line information (customers really > want this). Right, that would be nice. This should be synthesizable from the DebugLoc on the instruction in the asm printer, no need to redundantly encode it into the comment field. > - Tag instructions as register spills or reloads....

...t; I was attempting to reduce the number of files affected, but if you > > want this change I'll go ahead and do it. > > Makes sense, thanks. Please do it as a separate patch from the other > changes though since it will be large and mechanical. Ok, no problem. > > - Tag instructons with source line information (customers really > > want this). > > Right, that would be nice. This should be synthesizable from the > DebugLoc on the instruction in the asm printer, no need to redundantly > encode it into the comment field. Except the DebugLoc stuff isn't al...

...ominators and > modifies the IR. > > My guess is this is undesired/too heavyweight for inline cost > analysis, however the basic principle on how it renames things could > also be applied without IR changing for this specific case. Unlike > the EarlyCSE method, which is O(all instructons) PredicateInfo is > O(branches + number of uses of variables affected by conditions) > Without going into futher details, if all you care about is "for each > condition, give me the set of possibly affected variables" (so you can > see if they may simplify), we could do t...

On Jul 10, 2009, at 3:05 PM, David Greene wrote: > Here's the first of several patches to get comments into asm > output. This one > adds comment information to MachineInstructions and outputs it in the > generated AsmPrinters. This includes TableGen work to trigger the > comment > output in the right places. A couple of things are important to discuss: +

Here's the first of several patches to get comments into asm output. This one adds comment information to MachineInstructions and outputs it in the generated AsmPrinters. This includes TableGen work to trigger the comment output in the right places. Please review and comment. -Dave -------------- next part -------------- A non-text attachment was

All, I'm working on an improvement to the inline cost model, but I'm unsure how to proceed. Let me begin by first describing the problem I'm trying to solve. Consider the following pseudo C code: *typedef struct element { unsigned idx; } element_t; * *static inline unsigned char fn2 (element_t *dst_ptr, const element_t *a_ptr, const element_t *b_ptr,

On Jul 13, 2009, at 10:02 AM, David Greene wrote: >>> - Tag instructons with source line information (customers really >>> want this). >> >> Right, that would be nice. This should be synthesizable from the >> DebugLoc on the instruction in the asm printer, no need to >> redundantly >> encode it into the comment field. > >...

...PredicateInfo, but it requires dominators and modifies the IR. My guess is this is undesired/too heavyweight for inline cost analysis, however the basic principle on how it renames things could also be applied without IR changing for this specific case. Unlike the EarlyCSE method, which is O(all instructons) PredicateInfo is O(branches + number of uses of variables affected by conditions) Without going into futher details, if all you care about is "for each condition, give me the set of possibly affected variables" (so you can see if they may simplify), we could do that very very quickly (a...

...guess is this is undesired/too heavyweight for inline > cost analysis, however the basic principle on how it > renames things could also be applied without IR changing > for this specific case. Unlike the EarlyCSE method, which > is O(all instructons) PredicateInfo is O(branches + number > of uses of variables affected by conditions) Without > going into futher details, if all you care about is "for > each condition, give me the set of possibly affected > variables" (so you...