search for: oox

.... Again, it would be helpful if you included example output to >> show what you're going for. > > Ok, here's an example: > > movl (%rsi), %ecx # LLVM > Instruction: volatile store i32* %ksize, i32** %ksize3 ; > [oox.4 : sln.5] > > # > [result] Pattern > 1367 Instead of printing 1367, why not print "MOV32rm" like -print- machineinstr does? If you really want 1367, just print MI- >getOpcode(). The asmprinter definitely ha...

...at an earlier pass > would. Again, it would be helpful if you included example output to > show what you're going for. Ok, here's an example: movl (%rsi), %ecx # LLVM Instruction: volatile store i32* %ksize, i32** %ksize3 ; [oox.4 : sln.5] # [result] Pattern 1367 I then hacked tblgen to output this in the generated isel file: // Pattern 1367: (ld:i32 addr:iPTR:$src)<<P:Predicate_load>> // Emits: (MOV32rm:i32 addr:iPTR:$src) PatternID =...

...an you don't get line numbers :). You're right, it's not a big hurdle. > > Ok, here's an example: > > > > movl (%rsi), %ecx # LLVM > > Instruction: volatile store i32* %ksize, i32** %ksize3 ; > > [oox.4 : sln.5] > > > > # > > [result] Pattern > > 1367 > > Instead of printing 1367, why not print "MOV32rm" like -print- > machineinstr does? If you really want 1367, just print MI- > > >ge...

On Jul 13, 2009, at 1:58 PM, David Greene wrote: >>> Ok, here's an example: >>> >>> movl (%rsi), %ecx # LLVM >>> Instruction: volatile store i32* %ksize, i32** >>> %ksize3 ; >>> [oox.4 : sln.5] >>> >>> # >>> [result] Pattern >>> 1367 >> >> Instead of printing 1367, why not print "MOV32rm" like -print- >> machineinstr does? If you really want 1367, just prin...

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. > > Except the DebugLoc

On Monday 13 July 2009 11:40, Chris Lattner wrote: > > 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

Has anyone succeeded in producing Rails reports using jasper reports? I have prepared reports directly with Jasper''s iReport tool using my MySQL data. It is a very powerful reporting tool. The reports look greate. But I have not been able to produce the reports from my Rails application. I have followed the instructions provided at: