similar to: malloc error in tab-completion: OS X

I'm not sure if this is a bug or expected behavior, but I don't see anything in the documentation that explains it, so I thought I'd mention it: ~ michaelweylandt$ R -q --vanilla library(compiler) enableJIT(3) `+` # Throws an error `+` # Throws a warning `+` # Prints the primitive as expected sessionInfo() R version 2.14.1 (2011-12-22) Platform: i386-apple-darwin9.8.0/i386

Hi, One of my Macs is kept at 10.6.8 (with Xcode 3.2.6) because it's a system I still wish to support. However, I'd like to move to clang on it, if possible. I prefer to either install a precompiled binary distribution (if it exists) or compile it on my own, but for the moment I'd prefer to avoid installing it through macports. Looking at the LLVM releases downloads page, I see

On Nov 20, 2016, at 4:28 PM, Fred Turner <fred at c5consulting.net> wrote: >> Mac Pro Server 2012 >> Mac OS X Server 10.6.8 >> Dovecot 1.1.20apple0.5 The 2012 Mac Pro Server shipped with 10.7.3. Did you seriously hack 10.6.8 onto it?

On Dec 23, 2008, at 9:14 AM, Jon Harrop wrote: > I discovered that LLVM's malloc only allows a 32-bit size argument, > so you > cannot use it to allocate huge blocks on 64-bit machines. So I > considered > replacing all of my uses of LLVM's malloc instruction with calls to > the libc > malloc function instead. That got me wondering why LLVM even has its >

Chris Lattner wrote: > On Dec 23, 2008, at 9:14 AM, Jon Harrop wrote: >> I discovered that LLVM's malloc only allows a 32-bit size argument, >> so you >> cannot use it to allocate huge blocks on 64-bit machines. So I >> considered >> replacing all of my uses of LLVM's malloc instruction with calls to >> the libc >> malloc function instead.

>> There is no good reason for malloc to be an instruction anymore. I'd >> be very happy if it got removed. Even if we keep it, malloc/alloca >> should be extended to optionally take 64-bit sizes. > > I'm curious. Do we want to keep the free instruction? No, there's no reason to. -Chris

On Jan 12, 2009, at 8:24 AM, Dan Gohman wrote: > > On Jan 11, 2009, at 11:22 AM, Chris Lattner wrote: > >>>> There is no good reason for malloc to be an instruction anymore. >>>> I'd >>>> be very happy if it got removed. Even if we keep it, malloc/alloca >>>> should be extended to optionally take 64-bit sizes. >>> >>>

I discovered that LLVM's malloc only allows a 32-bit size argument, so you cannot use it to allocate huge blocks on 64-bit machines. So I considered replacing all of my uses of LLVM's malloc instruction with calls to the libc malloc function instead. That got me wondering why LLVM even has its own malloc intrinsic anyway... Am I correct in assuming that LLVM's malloc intrinsic

On Jan 11, 2009, at 11:22 AM, Chris Lattner wrote: >>> There is no good reason for malloc to be an instruction anymore. >>> I'd >>> be very happy if it got removed. Even if we keep it, malloc/alloca >>> should be extended to optionally take 64-bit sizes. >> >> I'm curious. Do we want to keep the free instruction? > > No,

On Jan 12, 2009, at 7:45 PM, Nick Lewycky wrote: >> isa<FreeInst>(X) can be replaced with: >> >> bool isFree(Instruction *X) { >> if (CallInst *CI = dyn_cast<CallInst>(X)) >> if (Function *F = CI->getCalledFunction()) >> if (F->isName("free") && F->hasExternalLinkage()) > > Surely you mean

Looking at tools/clang/lib/Driver/Tools.cpp , there's this fragment of code: if (Args.hasArg(options::OPT_rdynamic) && Version[0] >= 137) CmdArgs.push_back("-export_dynamic"); I built LLVM 3.4.2 from a OS X 10.11 "El Capitan" but specifying a fat build (386+x86_64) and requesting support back up to 10.6. It went fine, and the build passes all tests when run

Chris Lattner wrote: > On Jan 12, 2009, at 8:24 AM, Dan Gohman wrote: > >> On Jan 11, 2009, at 11:22 AM, Chris Lattner wrote: >> >>>>> There is no good reason for malloc to be an instruction anymore. >>>>> I'd >>>>> be very happy if it got removed. Even if we keep it, malloc/alloca >>>>> should be extended to

Hello, all. I have a two Mac mini 4.1 (mid 2010: Intel Core 2 Duo P8600, 4Gb RAM, NVIDIA GeForce 320M, Intel HDA) One has Snowleopard 10.6.8 (32-bit) installed, another - Lion 10.7.2 (64-bit). I have installed Wine 1.3.31 from MacPorts repository on both of them and attempts to run Civilization 4 Complete Edition. I've made dll substitution specific for this game using winetrics (msxml3,

Hi, I am using 32-bit R v 2.15.1, on Mac OsX v 10.6.8 with R GUI 1.52 Leopard build 32-bit (6188). I have also replicated this error on R 2.13.2 on a windows 7 machine. In some sequences of numbers, I am unable to use the which() function to index certain values. It seems to be primarily numbers with a 3 in the decimal. For example: > S=seq(0,4,0.01) > which(S==2.02) [1] 203 >

Hey guys, Earlier in this thread Oddsock said that a player recieving metadata it did not expect would most likely produce blips in the output. Has anyone checked any of these network dumps to see if any metadata is being sent? A while back I reported difficulty with playing Icecast2 streams through my TiVo. I recently upgraded to Beta 1 and the problem still exists. I don't want to

Dear list I have two (trivial) memory-questions related to a call with .C: If I allocate memory with R_alloc in a C-program (called with .C), will that memory "be taken from" the "available memory pool" (of a maximum of 4gb?) which R can allocate? (This is the impression I get from "Writing R extensions".) If instead I use malloc; will that memory then be taken

Hi, I am the maintainer for the compiz port on FreeBSD. We do not have strndup, so this patch replaces one other instance of strndup. thanks, robert. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Replace-strndup-with-malloc-and-strncpy.-FreeBSD-do.patch Type: application/mbox Size: 1671 bytes Desc: not available Url :

Hi Friends, how to allocate memory for a domU from some memory behind a PCI device. if the guest.conf used to boot up a domU specifies "memory=128", how to make sure that some of the memory pages get allocated from the range I specify. (the range is the memory behind a pci device). Please do send me your ideas/suggestions/questions, regards, Dinesh C

Hi Friends, how to allocate memory for a domU from some memory behind a PCI device. if the guest.conf used to boot up a domU specifies "memory=128", how to make sure that some of the memory pages get allocated from the range I specify. (the range is the memory behind a pci device). Please do send me your ideas/suggestions/questions, regards, Dinesh C

Hi, I am little bit interested in Wine source code. There is one thing I don't understand. How does HeapAlloc() work? Is it the same behavior as Winapi HeapAlloc()? If so then I have to check NULL value after each calling of this function, don't I? I have found this code in Wine 0.9.57: In dlls/dbghelp/stabs.c function 'static int stabs_new_include(const char* file, unsigned long