search for: nastiest

Hello, Several people have expressed interest in using LLVM to target MSP430 microcontrollers. Anton wrote an MSP430 backend as an exercise, and some of the nastiest parts are done (thanks Anton!), but the consensus seems to be that there's still quite a bit of work left to do before LLVM can replace the commercial and open-source compilers (IAR, CCE, CrossWorks, mspgcc, and so on) that people use. I've created a mailing list where we can have graphic,...

...e.table(mtcars, file="mtcars.txt") # write to text file (default is space-delimited) mtcars <- read.table(file="mtcars.txt") # read from text file and assign to an R object ## see help for all these functions as ?data ?read.table ## etc. ## end ## Data import/export is the nastiest step in any stats program, hold on ;^) ...and start with small examples: your "new" message probably means you don't have enough RAM (although from your post it is impossible to really tell). Giovanni Giovanni Millo Research Dept., Assicurazioni Generali SpA Via Machiavelli 4, 34132...

...how people get on with it before implementing the rest. Essentially, the library tries to abstract the simple-sounding task of recording who logged in and when away from the very ugly system-dependent implementation of this on various UNIX-like OSes. As Damien said before on the list, it's the nastiest part of porting OpenSSH to new platforms. The old record_login() function (login.c) is about 100 lines of code, full of #ifdef statements. The liblogin version is this: void record_login( <params> ) { struct logininfo *li; li = liblogin_alloc_entry(pid, user, host, ttyname); liblogin...

G'day, We are having problems when connecting to our Solaris 8 server Zeus from our Windows 2000 Terminal Servers. We are running Samba 2.2.8a on the unix box and are finding that from time to time people are having difficulty opening files from shares on this server. They also have difficulty mapping network drives. It reports errors such are "file doesn't exist". However, we

Using Office2K (Word & Excel) on NTWS 4.0 and samba 3.0.0 on Debian Linux, kernel 2.4.21. 1. Run Excel and create a sheet. Save it to the Samba server. No problem. 2. Close the sheet and open a new one (File->New). 3. Try to save the new sheet over the first one and Excel gives the error: "Cannot save the file. 'H:\test\Book1.xls' is not a valid file name." 4. Click

...t it is not possible for all of r0, r1, r2, and r3 to be equal to zero at the end of the test, assuming that a, b, c, and d are all initially zero, and the four functions above run concurrently? There are many similar litmus tests for other combinations of reads and writes, but this is perhaps the nastiest from a hardware viewpoint. Does SYNC_MB() provide sufficient ordering for this sort of situation? Another (more academic) case is this one, with x and y initially zero: void cpu0(void) { WRITE_ONCE(x, 1); } void cpu1(void) { WRITE_ONCE(y, 1); } void cpu2(void) { r1 = READ_ONCE(x,...

...that. First thing I'd try would be adding the 64-bit registers as a valid class for i32 ("addRegisterClass(MVT::i32, GPR64)"). If that works, you're good to go; if not, it should be possible add fake 32-bit registers and just print them the same as the 64-bit ones at the end. The nastiest hackery would be in the AsmParser, which may or may not be important. Cheers. Tim.

...ndt: 4. november 2003 02:20 > > On Tue, Nov 04, 2003 at 11:55:25AM +1100, DAVIES Rob wrote: > G'day, > > > We are having problems when connecting to our Solaris 8 server Zeus > > from our Windows 2000 Terminal Servers. > > I think you might be hitting two of the nastiest bugs with > that combination. > > Firstly, there are issues with Solaris 8, and TDB locks, for > which there is a solaris kernel patch (it's an fcntl issue). > But more importantly, there is an issue caused by the way > Windows Terminal Server clients connect - they all...

Hey Richhiey, Most probably Xapian is used with CYGWIN in Windows and Windows Specific Code in Xapian is based on CYGWIN, However we would be able to help you out with this issue, if you could pastebin whole 'gnu-make' generated report. Regards, Abhishek On Sat, Jan 3, 2015 at 5:30 PM, <xapian-discuss-request at lists.xapian.org> wrote: > Send Xapian-discuss mailing list

On 01/14/2016 01:29 PM, Paul E. McKenney wrote: > >> On 01/14/2016 12:34 PM, Paul E. McKenney wrote: >>> >>> The WRC+addr+addr is OK because data dependencies are not required to be >>> transitive, in other words, they are not required to flow from one CPU to >>> another without the help of an explicit memory barrier. >> I don't see any

On 01/14/2016 01:29 PM, Paul E. McKenney wrote: > >> On 01/14/2016 12:34 PM, Paul E. McKenney wrote: >>> >>> The WRC+addr+addr is OK because data dependencies are not required to be >>> transitive, in other words, they are not required to flow from one CPU to >>> another without the help of an explicit memory barrier. >> I don't see any

Hi, folks: I remain intrigued by the gap in BRI implementation between North America and Europe, and I wanted to get feedback from the list members on the matter. I'm seriously considering making the leap in our office. In Europe, the idea that an office that does not have enough lines to justify PRI would use analog lines is perceived as technologically backwards, and yet that's what

I am trying to prototype a back end for a new processor. It has a 64-bit datapath, so all registers are 64 bits and load instructions always extend to 64 bits. But the type 'int' is 32 bits, and arithmetic instructions have variants that operate on only the lower 32 bits of each register. So for a basic 'a = b + c' example, we get %0 = load i32, i32* @b, align 4, !tbaa !1 %1

I have just taken on a new site and they were running ruby on rails for their store. I have finally found the database but I cannot get the store to work. I can''t even get it to show up. I have never used this software before and have no idea where to start. All I know is the client was upset when I told them we wou;ld have to start a new store. They apparently have a few hundred of

The first one is the nastiest - it is an assertion failure caused by a spec-compliant client and introduced by our security fix that was released in 1.14.1. Eric Blake (4): server: Fix regression for NBD_OPT_INFO before NBD_OPT_GO server: Fix back-to-back SET_META_CONTEXT server: Forbid NUL in export and context names...