search for: applibs

Dear Tom, The express product makes standard windows api calls to the machine where it is installed to open, read, write to, and close files on the network. It does not, in any way tell samba how to react, it is simply telling Windows to open, read and write to the files on the network leaving how it is done to the underlying network protocols. Based on what I have seen it appears that Windows

Andrew: Thanks for the heads up. As always, the support you guys give to an open source product amazes me. We worked with Jeremy & John Terpstra a few years ago when there was a problem with how AutoCAD was creating lock files (AutoCAD R14 running against SAMBA 1.9.something; it ended up being a timing issue that AutoDesk & Microsoft resolved, as well as samba 2.0 provided an

...floating point immediate to a floating point register. def MOVF32fk : InstTCE<(outs F32Regs:$dst), (ins f32imm:$val), "$val -> $dst;", [(set F32Regs:$dst, (f32 imm:$val))]>; This causes an type contradiction: /home/hkultala26/src/devel/tce/src/applibs/LLVMBackend/plugin//TCEInstrInfo.td:109:1: error: In MOVF32fk: Type inference contradiction found, 'f32' needs to be integer def MOVF32fk : InstTCE<(outs F32Regs:$dst), (ins f32imm:$val), why? Why does llvm assume floating point immediate needs to be integer?