search for: xex

Dear list, I'm migrating a project from Matlab to R, and I'm facing a relatively complicated problem for nls. My objective function is below: >> objFun <- function(yEx,xEx,tEx,gamma,theta,kappa){ yTh <- pdfDY(xEx,tEx,gamma,theta,kappa) sum(log(yEx/yTh)^2) } The equation is yTh=P(xEx,tEx) + noise. I collect my data in: >> data <- data.frame(xEx,tEx,yEx) And I do the nls: aux <- nls( ~ objFun(yEx,xEx,tEx,gamma,theta,kappa), da...

...t much work. Using Clang's rewriter requires no real low-level maintenance, just creating and maintaining a C library for support functions emitted by the compiler (e.g. objc_msgSend). It seems to create a backend for LLVM targeting the 360 I wouldn't need to create something that outputs XEX's anyway. My custom backend would effectively create object files that the 360's linker would have to be able to recognize. This would mean not only outputting all the correct ABI conforming code but the correct PDB debugging information as well. It seems much less, and easier, work to im...

...e to source conversion. I don't know how it work yet, but if it is design to output code for the NeXT Runtime, you may have to tweak it to output code compatible with your runtim. > It seems to create a backend for LLVM targeting the 360 I wouldn't need to create something that outputs XEX's anyway. My custom backend would effectively create object files that the 360's linker would have to be able to recognize. This would mean not only outputting all the correct ABI conforming code but the correct PDB debugging information as well. It seems much less, and easier, work to im...

I'm slightly confused here, just to be clear: you're planning to go ObjC -> LLVM (via Clang or whatever) -> C, then use the 360 SDK compiler to build that, right? If that's the case, I think it'd be a better option than to use LLVM to directly generate XEXs, and you won't give the TCR guys fits (I checked the BAS TCRs, none of them say you can't do that, but the platform has some requirements regarding binary code that I doubt you'll get right without a lot of effort). If that is the pipeline you had in mind, have you attempted to run a H...

...The network interface is a Broadcom NetXtreme BCM5751M PCI express. I have the problem on both RHEL5 and SUSE SLES 10 but I am troubleshooting it on RHEL. When I run the standard kernel, the eth0 interface works absolutely fine with either DHCP or a static IP address. When I boot the XEX kernel, eth0 fails to initialize and therefore does not end up with an IP address via DHCP. I have tried giving it a static IP which works which allows eth0 to initialize, but I still can''t use the interface (pinging my router at 192.168.1.1 fails) My XEN kernel is :2.6.18.8.1.4 XEN...

...168.110) for port 8002. ## If I try to migrate to localhost (xm migrate slack-1 localhost) it work! The 2 dom0 machine are on the same subnet. The VM disk is on NFS export. I''ve no idea of the problem. Anyone can help me? Thanks. nick PS: the OS is Linux Slackware 10.2, kernel 2.6.16-xex. -- Nicola Bianchi System Administrator _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

We are looking at using Objective-C/C++ in a new game engine.  Objective C's duality of being both very dynamic and very "C" gives us exactly what we need to make the SDK and engineering of games simpler. This means that we will need a way to compile it on all platforms our games will target.  Currently the major platforms we are concerned with include... PC, Mac, XBox 360, PS3,

Hello, I've a problem with conversion from any charset to 1251. I think there is no support of 1251 codepage at all, only KOI8-R and 866 from cyrillic. xex what can i do, to solve the promblem with russian charset ? Samba resolves russian charset on freebsd perfectly (in log files), the problem is with display charset param it should be 1251 i hope, to reflect correctly. my sys conf: FreeBSD-4.8 samba-3.0.0 ooficial release thanks