search for: gigante

Il giorno 18/mar/2013, alle ore 15:14, Óscar Fuentes <ofv at wanadoo.es> ha scritto: > Nicola Gigante <nicola.gigante at gmail.com> writes: > >> The error I get is the following: >> Undefined symbols for architecture x86_64: >> "typeinfo for llvm::FoldingSetImpl", referenced from: >> typeinfo for llvm::FoldingSet<Type> in Program.o >> ld...

I've discovered recently that something on my Centos 5.8 box (up to date) is hogging a ton of RAM. so a little while ago I sat and watched top for a while. it showed (sorry, I didn't take screen shots or write this down, so the numbers are a bit rough) that out of 8 gigs of swap, around 2 1/2 was in use, and all the RAM (except for the little the kernel keeps for itself) was in use

Nicola Gigante <nicola.gigante at gmail.com> writes: > The error I get is the following: > Undefined symbols for architecture x86_64: > "typeinfo for llvm::FoldingSetImpl", referenced from: > typeinfo for llvm::FoldingSet<Type> in Program.o > ld: symbol(s) not found f...

Nicola Gigante <nicola.gigante at gmail.com> writes: > Il giorno 18/mar/2013, alle ore 15:14, Óscar Fuentes <ofv at wanadoo.es> ha scritto: > >> Nicola Gigante <nicola.gigante at gmail.com> writes: >> >>> The error I get is the following: >>> Undefined symbo...

Nicola Gigante <nicola.gigante at gmail.com> writes: >> Adding an option for enabling RTTI on the cmake build is trivial. Dunno >> about the `configure' build. You can try filing a feature request on >> Bugzilla. > > Ok, I've managed to refactor some code and remove uses of...

On 09/08/19 18:24, Matthew Wilcox wrote: > On Fri, Aug 09, 2019 at 07:00:26PM +0300, Adalbert Laz?r wrote: >> +++ b/include/linux/page-flags.h >> @@ -417,8 +417,10 @@ PAGEFLAG(Idle, idle, PF_ANY) >> */ >> #define PAGE_MAPPING_ANON 0x1 >> #define PAGE_MAPPING_MOVABLE 0x2 >> +#define PAGE_MAPPING_REMOTE 0x4 > Uh. How do you know page->mapping would

On 09/08/19 18:24, Matthew Wilcox wrote: > On Fri, Aug 09, 2019 at 07:00:26PM +0300, Adalbert Laz?r wrote: >> +++ b/include/linux/page-flags.h >> @@ -417,8 +417,10 @@ PAGEFLAG(Idle, idle, PF_ANY) >> */ >> #define PAGE_MAPPING_ANON 0x1 >> #define PAGE_MAPPING_MOVABLE 0x2 >> +#define PAGE_MAPPING_REMOTE 0x4 > Uh. How do you know page->mapping would

Hello I'm trying to link my project with llvm 3.2 libraries. I haven't touched the project for some months. Previously I used to link to an svn build of llvm 3.1 and everything worked fine. I've compiled llvm with ./configure --enable-libcpp --enable-cxx11 Currently I'm only using StringRef, SmallVector and FoldingSet, so I only link libLLVMSupport and libLLVMCore. Are they

Il giorno 18/mar/2013, alle ore 18:47, Óscar Fuentes ha scritto: > > You can try building LLVM with > > CXXFLAGS=-frtti configure .... > CXXFLAGS=-frtti make ... > > I'm not sure if CXXFLAGS takes precedence over the hard-coded -fno-rtti > in the makefiles, though. > > With the cmake build, you can try as above (but replacing `configure' > with

Hi all. I’ve heard a couple of times that some of the problems solved by various passes in the optimizer are indeed NP-hard, even though the instances are small enough to be tractable (and very quickly). Is this true? If so, which are these problems? Register allocation? Instruction scheduling? Are they solved exactly or by approximations? Or not solved at all (the need of solving them is

>>> >>> Great! Seems to be working fine for my usage and makes my configs 50% >>> smaller (which is gigantic improvement). Will do more testing though. >>> >>> Thanks! >>> >>> A little bit offtopic, but what is the point of using imap/pop SNI? All clients want to connect to their own domain or what? -- Kaspars

https://bugzilla.samba.org/show_bug.cgi?id=7246 Summary: max-size not working in 3.0.7 built from source with default configure Product: rsync Version: 3.0.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

On 11.11.2016 19:17, Arkadiusz Mi?kiewicz wrote: > On Friday 11 of November 2016, Aki Tuomi wrote: > >> If you are interested in testing, please find patch attached that allows >> you to specify >> >> local_name *.foo.bar { >> } >> >> or >> >> local_name *.*.foo.bar { >> } >> >> so basically you can now use certificate

Alguien sabe donde puedo encontrar algun datasheet gigante, de más de 5 gigas, para poder practicar con grandes volumenes de información? Lo que quiero es probar a cargarlos con h20 y crear modelos con ellos. Me gustaria sobretodo problemas de clasificación... Gracias Jesús [[alternative HTML version deleted]]

As an absolute beginner, still reading "Modern Applied Statistics with S" and exercising with its examples, I'm frequently stopped by what it looks to be R poor help system (or is it my gigantic ignorance?). I mean that using help many arguments of a command seems to be given for granted like for instance: ............................... ?lines lines(x, ...) ## Default S3

So I got a new Pocket PC this weekend (yes, you read that right, sorry, don't like the Palms on offer currently and I can at least install software on it via Windows on VMWare). One of the main things I wanted to do with it is get Audible.com again and listen to All Things Considered from NPR on the way home like I used to. Now I find out they not only don't have an agreement with Audible

> > Is this what you mean? Is there any reason to keep the .bc files distinct > > like a ".a" file, or is it ok for your purposes to link them together into > > a single unit, like a ".so" file? > > Well, the answer depends on whether the individual modules are > separately loadable or not. Suppose the resulting bytecode file gets JIT > loaded

2015-08-17 11:26 GMT-07:00 Mehdi Amini <mehdi.amini at apple.com>: > Hi, > > On Aug 17, 2015, at 12:13 AM, deadal nix via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > 2015-08-16 23:21 GMT-07:00 David Majnemer <david.majnemer at gmail.com>: > >> >> >> Because a solution which doesn't generalize is not a very powerful

Dear llvm-dev, As I've been working with llvm sources on a prototype backend, it seems to me that much of the documentation on llvm internals is, shall we say, wanting. (I'm looking at you particularly, tablegen.) I can clean up documentation issues and clarify in the .rst files as I'm learning, but the code submission process is silent on how documentation changes make it into

Based on the examples I've seen in using statistical analysis packages such as lmer, it seems that people usually tabulate all the input data into one file with the first line indicating the variable names (or labels), and then read the file inside R. However, in my case I can't do that because of the huge amount of imaging data. Suppose I have a one-way within-subject ANCOVA with