search for: davidm

...? Somehow apple's version bypasses smbpasswd and authenicates directly with netinfo...Any ideas? I can dump netinfo information into a passwd file and create an smbpasswd file from that, but it won't be dynamic when users change their password. Thanks, David -- David MacAlpine email:davidm@mit.edu Dept. of Biology RM 68-640 phone:(617)253-1979 Massachusetts Institute of Technology fax:(617)253-4043 77 Massachusetts Avenue Cambridge, MA 02139

...n"); And at runtime I see that the LLVMTypeOf is corresponds to LLVMPointerTypeKind. ./app Is a Function Type is: 12 For reference: Function: 9 Pointer: 12 Assertion failed: (isa<X>(Val) && "cast<Ty>() argument of incompatible type!"), function cast, file /Users/davidm/code/contrib/llvm/llvm/include/llvm/Support/Casting.h, line 237. Shouldn't this be a function type? I also can't seem to find how to learn what type it points to - LLVMPointerType() appears to create a new pointer-to-X but is there no getter to find what X is for this pointer in hand?...

...ibit this behaviour, I had to use my own recent svn tree) $ clang -arch arm -emit-llvm -S -O0 example.c -o arm.bc $ opt -print-after-all -O1 arm.bc I can see where the branch test is whittled down to an 'if true' and then eliminated, but cannot comment as to why this might be. Cheers, -DavidM On 05/06/2013, at 9:50 AM, Carl Norum <carl at lytro.com> wrote: > > On Jun 4, 2013, at 4:42 PM, Tyler Hardin <tghardin1 at catamount.wcu.edu> wrote: >> I was suggesting to add it to the function, like >> volatile void func(..); >> Theoretically, this would te...

...eturning to my main function. Is there anything obvious I've missed? Sorry for the long mail but I figure if I put all my data, then where I went wrong would be more obvious to someone who knows what they're doing :) Thanks, and please let me know if there's anything extra I can add. -DavidM PS: below is my complete source. #include <stdio.h> #define __STDC_LIMIT_MACROS #define __STDC_CONSTANT_MACROS #include "llvm-c/Core.h" #include "llvm-c/ExecutionEngine.h" int main(int argc, const char * argv[]) { LLVMContextRef llvm; llvm = LLVMContextCreate...

...eturning to my main function. Is there anything obvious I've missed? Sorry for the long mail but I figure if I put all my data, then where I went wrong would be more obvious to someone who knows what they're doing :) Thanks, and please let me know if there's anything extra I can add. -DavidM PS: below is my complete source. #include <stdio.h> #define __STDC_LIMIT_MACROS #define __STDC_CONSTANT_MACROS #include "llvm-c/Core.h" #include "llvm-c/ExecutionEngine.h" int main(int argc, const char * argv[]) { LLVMContextRef llvm; llvm = LLVMContextCreate...

On Jun 4, 2013, at 4:42 PM, Tyler Hardin <tghardin1 at catamount.wcu.edu> wrote: > I was suggesting to add it to the function, like > volatile void func(..); > Theoretically, this would tell the compiler not to omit seemingly superfluous calls to func. 'volatile' can't apply to a function, so I'm not sure what you mean. In your example, 'volatile' modifies

I am having an issue on my integration server currently. When I run rake spec locally my specs run and all is good but when I run rake spec in on my integration box I get the following output Options written to spec/spec.opts. You can now use these options with: spec --options spec/spec.opts When I run spec --options spec.opts I get the same message. script/spec and others all do the same , if I

...extension. > > In any case, thanks for working on R! I was excited to find that I > now have to option to use the S language on my Linux systems! > > Cheers, > > --david > > -- > David Mosberger, Ph.D; HP Labs; 1501 Page Mill Rd MS 1U17; Palo Alto, CA 94304 > davidm@hpl.hp.com voice (650) 236-2575 fax 857-5100 > -- O__ ---- Peter Dalgaard Blegdamsvej 3 c/ /'_ --- Dept. of Biostatistics 2200 Cph. N (*) \(*) -- University of Copenhagen Denmark Ph: (+45) 35327918 ~~~~~~~~~~ - (p.dalgaard@bios...

...______________________ > > fxruby-users mailing list > > fxruby-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/fxruby-users > > > ------------------------------ > > Message: 5 > Date: Fri, 13 Feb 2009 21:43:20 -0800 > From: David MacMahon <davidm at astro.berkeley.edu> > Subject: Re: [fxruby-users] install.rb:655:in `command'': > system("make") failed (RuntimeError) > To: fxruby-users at rubyforge.org > Message-ID: <C95732A1-4CDF-4AC3-A04A-6329B873007B at astro.berkeley.edu> > Content-Type:...

Hi I didn't get bridgeing to work with Linux kernel 2.6.10 (coldfire 5485) yet. When i try to configure bridgeing with "brctl", everything seems to be ok, but i if i try to ping through my bridge, i see ARP-Request arriving on the other side, but the ARP-Responses do not go back through the bridge. Now i could read in

I've been a R-user for quite some time. The graphic on the home page looks a bit in need of polish so I applied some antialiased transformations that Peter Dalgaard has previously posted to R-help for improving graphic quality. I had to change the margins a bit, but here is what it looks like: http://www.broad.mit.edu/~finnyk/Rhome.jpg Personally, I think it looks much better. Because

Hi, I'm wanting to call R from Perl via the RSPerl package. However I cannot seem to install it on my Macbook (OS X Tiger - R 2.6 - Perl 5.8.6). I try to install the source downloaded from the sigmahat website - but it seems to fail - when I search my system for R.pm - I can't find it? Something looks to be going wrong with the make bits? Cheers David M ---- $ R CMD INSTALL

Hi. I rewrote the patch according to the comments. I adopted generating in-place code because it looks the quickest way. The point Eddie wanted to discuss is how to generate code and its ABI. i.e. in-place generating v.s. direct jump v.s. indirect function call Indirect function call doesn't make sense because ivt.S is compiled multi times. And it is up to pv instances to choose in-place

Hi. I rewrote the patch according to the comments. I adopted generating in-place code because it looks the quickest way. The point Eddie wanted to discuss is how to generate code and its ABI. i.e. in-place generating v.s. direct jump v.s. indirect function call Indirect function call doesn't make sense because ivt.S is compiled multi times. And it is up to pv instances to choose in-place

The following dump-core patches changes its format into ELF, adds PFN-GMFN table, HVM support, and adds experimental IA64 support. - ELF format Program header and note section are adopted. - HVM domain support To know the memory area to dump, XENMEM_set_memory_map is added. XENMEM_memory_map hypercall is for current domain, so new one is created. and hvm domain builder tell xen its

...ity > to client machines, but Samba doesn't support the > server-side functionallity, IIRC, at least when Samba > is running as a PDC. Oh, I guess that hasn't been merged from samba-tng yet. :( Sorry, I haven't been keeping up on 2.2 and PDC support... Mike Return-Path: <davidm@comrad.co.nz> Delivered-To: samba@lists.samba.org Received: from mailhost.comrad.co.nz (smtp.radiology.net.nz [210.54.249.27]) by lists.samba.org (Postfix) with ESMTP id 15E744AB3 for <samba@lists.samba.org>; Wed, 8 Aug 2001 14:34:41 -0700 (PDT) Received: from david (david.comrad.co.n...

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Now all the comments so far have been addressed, but only a few exceptions. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops.

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Now all the comments so far have been addressed, but only a few exceptions. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops.

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Please review and comments. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops. Currently only ia64/xen pv_ops implementation

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Please review and comments. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops. Currently only ia64/xen pv_ops implementation