similar to: problem with read.table( )

Hi folks, on CentOS 6.5 I run tripwire software which verifies data integrity. My system is automatically updated by yum (as far as I understand the /etc/cron.daily/0yum.cron is responsible for the regular system updates). After a system update I'm then notified by tripwire about the changes on the file system. By browsing those tripwire reports I found that there are files which did

Hello, I have a server running samba version 4.7.1 on centos 7.5 1) A series of operations by a windows 10 (up to date) pc client consisting of  searching (or browsing)/opening/modifying/closing a (each time different) file multiple times on a samba share containing many files (more than 11000) goes fast for a while. 2) Then the same operation (or just the searching or opening) of the same user

Hello, every one, Using the qt() function in R, I got a different Student t-value with the Student t table. e.g. the return value of function qt(0.95,9) is 1.833, while in table it is 2.262. I do not know why the difference exists. I guess it may be a bug in R. -- Íõ»¯Èå ²©Ê¿Ñо¿Éú ±±¾©Ê¦·¶´óѧ¾°¹ÛÉú̬Óë¿É³ÖÐøÐÔ¿ÆѧÑо¿ÖÐÐÄ ±±¾©Êк£µíÇøнֿÚÍâ´ó½Ö19ºÅ±±¾©Ê¦·¶´óѧÉúÃü¿ÆѧѧԺ 100875 Huaru

>> One nit-pick, I see that some of the interfaces use tons of parameter, >> which is something I'd like reduce for ease of use. > >Right. It was my concern as well, but I eventually decided to write it >this way. Feel free to change it. > As we are speaking about modifying the lib, here are two things I would like to modify/add in it: - Replacing depedency

Hi, Duncan > /usr/X11R6/bin/ld: i386:x86-64 architecture of input file `/usr/lib/../lib/crti.o' is incompatible with i386 output > /usr/X11R6/bin/ld: i386:x86-64 architecture of input file `/usr/lib/../lib/crtn.o' is incompatible with i386 output > make[4]: *** [32/libgcc_s.so] Error 1 This is multilib issue. Please read README.LLVM file, I added section there describing possible

On Thursday 12 November 2009 22:48, Chris Lattner wrote: > > There is also the question of whether intptrs should be allowed as > > *members* of vectors. I have no opinion on this, except to say that > > it probably only makes sense in situations where you can also have > > vectors of pointers. > > Vectors of pointers are not allowed. I think disallowing intptr in

> Are these known to be broken right now? I get failure when using either. > > $ llc -march=arm -print-machineinstrs hw.bc Seems due to David's patches. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Nov 13, 2009, at 10:16 AM, Samuel Crow wrote: > Hello all, > > My partner was just debugging a project that had tried to call a > function without arguments in the code but the declaration wasn't > declared with a void parameter list. It failed with an assertion > that something was trying to ++ past the end of an ilist. > > I seem to remember Chris Lattner

Are there any known inheritance graphs of all the classes? That definitely would help in trying to understand the interactions between everything. Micah ________________________________ From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Evan Cheng Sent: Wednesday, September 10, 2008 10:32 PM To: LLVM Developers Mailing List Subject: Re: [LLVMdev]

Good day, Firstly, I am very new to this project. I have dug through some of the documentation, but cannot find a satisfying answer to some questions I have. I hope somebody here can edify me. I am interested in embedded a LLVM 'VM' inside an embedded ARM-based device. That is, I want to be able to load and execute .bc files directly in an embedded system. The questions: -

Please use subjects that have something to do with the content, this discussion has nothing to do with 2.4 On Oct 11, 2008, at 1:01 PM, OvermindDL1 wrote: > On Sat, Oct 11, 2008 at 1:24 PM, Kenneth Boyd <zaimoni at zaimoni.com> > wrote: >> /* snip */ > > Actually, my biggest issue with llvm (which highly impacts testing as > well) is the use of abort()... > I

Hello again, I had hoped that rc4 would be the last one, but I wanted to pick up one more fix, so here we go. Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the release branch at 35627038123. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc5 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 If nothing new comes up, I plan to tag

Hi, > I am confused. Shouldn't the gcc 4.2 front-end build behave > just like the FSF gcc build. The first stage builds the compilers > and the second stage rebuilds them using those from the first > stage? the FSF gcc requires you to build the C compiler (I think - will check). Thus a newly built C compiler is always available to build later stages. We can't reasonably

Hi, I didn't know that about bitcast. This becomes important if someone wants a pointer to a vector element as we would either need to support the bistcast or we just don't allow that. For most vector code that I'm aware of, no one really wants to take an address of vector element as by doing so, one is kind of scalarizing the vector which would be bad for performance. If

Hans Wennborg wrote: > After discussing with Nick Lewycky in the IRC channel, here comes a less > aggressive patch. > > We were worried that a constant pointer could alias with a GlobalValue. > Also, if one pointer could be a GlobalValue and the other a GlobalAlias > with the GlobalValue as aliasee. > However, I was not able to produce a test where this happens wihout the

DO YOU WANT TO MAKE EASY MONEY? I found this on a bulletin board and decided to try it. A little while back, I was browsing through newsgroups, just like you are now, and came across an article similar to this that said you could make thousands of dollars WITHIN WEEKS with only an initial investment of $6.00! So I thought, "Yeah right, this must be a scam", but like most of us, I was

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!-- #msg dl { border: 1px #006 solid; background: #369; padding: