search for: instructino

...;; def IFEQ : Unknown<"if =0 goto">; def IFNEQ : Unknown<"if <>0 goto">; ..... Should this work? > Also, if you haven't already, you might want to teach TargetInstrInfo > that '=' is a move instruction (implement isMoveInstr), so instructinos > like 'gr1 = gr1' will go away and you'll get coallescing. :) BTW, is it possible to set some instruction flag, instead of overriding a function? Something like: let isMove = 1 in def MOVE :..... ? - Volodya

..... aka add {} Also, if you do 'tblgen target.td' it will spit out all of the records to stdout so you can visually inspect them. > > Also, if you haven't already, you might want to teach TargetInstrInfo > > that '=' is a move instruction (implement isMoveInstr), so instructinos > > like 'gr1 = gr1' will go away and you'll get coallescing. :) > > BTW, is it possible to set some instruction flag, instead of overriding a > function? Something like: > > let isMove = 1 in > def MOVE :..... That would make sense, but no not currently...

...#39;if <>0 goto LBB11;' things will probably magically start working for you, as the copies will be inserted BEFORE the branch instead of after it. Also, if you haven't already, you might want to teach TargetInstrInfo that '=' is a move instruction (implement isMoveInstr), so instructinos like 'gr1 = gr1' will go away and you'll get coallescing. :) -Chris > I also attach the debug dumps from my backend. > > The basic block in question is shortcirc_done.1 (line 198 in the log). It > starts with: > > %reg1060 = phi %reg1032, mbb<shortcirc_next....

...hat reassociation would be valid even on non-constant values. It's not clear whether you meant to contradict that here. [...] > -fp-contract=<value> > I'm not too familiar with this option, but I recommend that 'all' turn > on the > 'F' bit for all FP instructinos, default do so when following the > pragma, and > off never doing so. This option should still be passed to the backend. > Please coordinate with Lang and others who have already done a fair amount of work on FP_CONTRACT. > > (Optional) > I propose adding the below flags: &g...

...g point instructions. If this flag doesn't already cause clang to run llc with -enable-unsafe-fp-math, then I propose that it does so as well. -fp-contract=<value> I'm not too familiar with this option, but I recommend that 'all' turn on the 'F' bit for all FP instructinos, default do so when following the pragma, and off never doing so. This option should still be passed to the backend. (Optional) I propose adding the below flags: -ffinite-math-only Allow optimizations to assume that floating point arguments and results are NaNs or +/-Inf. This may produce...

Folks, I'm running into something which looks like a bug in linearscan allocator. Of course I can't be 100% sure it's not some unobvious mistake on my part, so I'd like to hear your opinion. First, I attach two files -- LLVM asm and the asm for my target. The problem with assembler is: on line 171 it uses register gr2, which is copied from gr6 above, on line 161. The only

...Allocas, "Number of unsafe static allocas"); +STATISTIC(NumUnsafeDynamicAllocas, "Number of unsafe dynamic allocas"); +STATISTIC(NumUnsafeStackRestorePoints, "Number of setjmps and landingpads"); + +} // namespace llvm + +namespace { + +/// Check whether a given alloca instructino (AI) should be put on the safe +/// stack or not. The function analyzes all uses of AI and checks whether it is +/// only accessed in a memory safe way (as decided statically). +bool IsSafeStackAlloca(const AllocaInst *AI, const DataLayout *) { + // Go through all uses of this alloca and check whe...