search for: prodic

Hello, I've just installed Wine (on Ubuntu 10.04 LTS) and a software called VCCorp ProDict 2007. It succeed but after some seconds running, Wine displays an error and stop program. I use WINEDEBUG and it shows: Code: hoa at ubt:~$ WINEDEBUG=+loaddll wine '/home/hoa/.wine/drive_c/Program Files/VCCorp/ProDic 2007/ProDic.exe' trace:loaddll:load_builtin_dll Loaded L"KERNEL32....

Hello, in R-2.1.0 I'm trying to prodice trellis plots from an lmList object as described in the help for plot.lmList. I can generate the plots from the help, but on my own data plotting fails with an error message that I cannot interpret (please see below). Any hints are greatly appreciapted. kind regards, Arne > dim(d) [1] 575...

2012/1/18 Jakob Stoklund Olesen <stoklund at 2pi.dk>: > This should work: > %1 = call i64 asm "call __ftol2", "=A,{st},~{dirflag},~{fpsr},~{flags},~{st}" (double %x) nounwind Thanks Jakob, the ~{st} constraint does the trick. It wasn't clear to me that "clobbers" means "pops" for x87 registers. -Joe

2012/1/18 Jakob Stoklund Olesen <stoklund at 2pi.dk>: > This should work: > %1 = call i64 asm "call __ftol2", "=A,{st},~{dirflag},~{fpsr},~{flags},~{st}" (double %x) nounwind Forgive me for being slow, but what would be the best way to implement the equivalent of that inline asm as a custom lowering for an instruction? Can I just create a CallInst and tell it to

...way to implement > the equivalent of that inline asm as a custom lowering for an > instruction? Can I just create a CallInst and tell it to lower that > instead, or do I need to replicate the functionality manually as DAG > nodes? On second thought, it might not be the best approach to prodice inline asm during lowering. How many of these libcalls do you need to implement? What exactly is the calling convention? Which registers are clobbered etc. /jakob

Is there any dump utility that exists for vorbis streams? What I am intersted in is something that will do a break down like: How many bits are used for encoding _each_ codebooks, how many bits are used for the residue, how much is used for the lpc coefficints. A selective dump of the codebooks themselves would be nice too of course. I'm wondering if anyone has such a little dump utility.