search for: backwardness

Hi, all -- I''m in the process of configuring a new machine for use as a Xen server, and am having some rather significant stability issues. The hardware/distro/kernel info is: opensuse 10.3 Linux offxen2 2.6.22.5-31-xen #1 SMP 2007/09/21 22:29:00 UTC x86_64 x86_64 x86_64 GNU/Linux 2 x Dual-Core AMD Opteron(tm) Processor 2212 HE 8 x 2GB PC2-5300 RAM Xen 3.1.0_15042-51 I currently have

It''s everytime when cpufreq_ondemand or cpufreq-set changes the frequency, aprox. 3 messages per event. Is that occasional? I tend to say: no. Please see an excerpt below. And if it''s not occasional, what could I do? And by the way: I found no code that TSC will get adjusted, so I think it will get worse over the time... Thanks, Carsten. messages.0:Jan 9 12:25:15 data kernel:

Hi Guus, I know this comes up from time to time. So it is time to update our expectations. Is there a roadmap for a 1.1 backward compatibility already? -rsd -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20141228/fcb2b44a/attachment.html>

Dear R-helpers: Hours ago, I asked how to replace a single forward slash with a double backward slash and recieved great help. Thanks again for all the repliers. In the meantime, I wonder how to replace a single backward slash with a double backward slash? e.g., I want change "c:\test" into "c:\\test" I tried the following but does not work.

I have a high end IBM system with 4 HT CPUs, am running xen-unstable with only Dom0 active, and I get lots of "Timer ISR/n: Time went backwards" messages. This is a short segment from dmesg: Timer ISR/1: Time went backwards: -259000 4465110000000 9741000 4465120000000 Timer ISR/6: Time went backwards: -224000 4465110000000 9776000 4465120000000 Timer ISR/6: Time went backwards: -159000

OK.. So I synced the clock.... and got .... dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards ( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the

While trying to compile an existing codebase which uses handwritten assembly with LLVM, I ran into an issue around using backward references in assembly absolute expressions. A simple example can be the following snippet: _foo: .fill 0x100 _bar: .fill _bar - _foo _baz: .fill 0x100 While gas compiles this snippet without any errors, the integrated assembler throws an error: expected

Dear fellow Xen''ers! I''m having a problem with my new Xen-enabled colocation server.. I hope ( at least ;) ) one of you guys know how to fix this problem.. For a certain amount of time ( 1-2 days ) the domU runs fine.. until the console starts spitting out messages like these: [80182.004456] clocksource/0: Time went backwards: delta=-6917292717540055641 shadow=80182004054805

Hello, How can I run a backward stepwise regression with part of the variables fixed, while the others participate in the backward stepwise analysis? Thank you, Einat -- View this message in context: http://r.789695.n4.nabble.com/Stepwise-analysis-with-fixed-variables-tp4650015.html Sent from the R help mailing list archive at Nabble.com.

The error we are getting is: "Undefined Form Value: 25" We have customers that have a variety of debuggers, and we need to be able to preserve Dwarf3 compatibility. GDB, Lauterbach, etc. The patch that caused a problem for us is: https://llvm.org/viewvc/llvm-project/llvm/trunk/lib/CodeGen/AsmPrinter/DwarfCompileUnit.cpp?r1=162493&r2=162526&pathrev=162526&diff_format=h

On Sun, Dec 28, 2014 at 10:33:47AM -0200, Raul Dias wrote: > I know this comes up from time to time. So it is time to update our > expectations. > > Is there a roadmap for a 1.1 backward compatibility already? The roadmap looks like this: 1.1pre1: backwards compatible with 1.0.x 1.1pre2: backwards compatible with 1.0.x, but not 1.1pre1 ... 1.1preN: backwards compatible with 1.0.x,

And how distant are we from a 1.1.0? :) On Sun, Dec 28, 2014 at 10:49 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sun, Dec 28, 2014 at 10:33:47AM -0200, Raul Dias wrote: > > > I know this comes up from time to time. So it is time to update our > > expectations. > > > > Is there a roadmap for a 1.1 backward compatibility already? > > The roadmap

> Would like to discuss: > 1) What level of interest is there in Dwarf backward compatibility; I don't have a lot of interest in keeping dwarf backward compatibility past my ability to test things, hence the option for darwin's gdb. That said if people want to have more strict options I can easily keep the dwarf stuff I'm working on inside of that framework. > 2) What levels

Hello John et al - I have been struggling to implement static backwards slicing with LLVM. After digging llvmdev postings for some time, I see that other people were having similar difficulties and John's got almost complete code that may be shared. May I get a copy of it, too? Better yet, it would be helpful for many other people if the code were checked in to an example directory or

Thanks John. I appreciate your help and I look forward to obtaining the code. A proper LLVM sub-project: No rush on this and please take your time. Thanks. - Jin -----Original Message----- From: Criswell, John T [mailto:criswell at illinois.edu] Sent: Saturday, October 08, 2011 11:58 AM To: Jinwook Shin; llvmdev at cs.uiuc.edu Subject: RE: interprocedural static backwards slicing Dear Jin,

Dear Jin, I've talked with Vikram, and we agree that having this code (and a dynamic backwards slicing pass that Swarup and I wrote) in a publicly available SVN repository is a good thing. I'll try to get you a copy of the static slicing code some time next week (I should be able to work on it Monday morning) so that you can start working with it right away. I can work on making a

Hi, I’ve noted some change in wording on the current (4.0) developer policy[1], compared to the 3.9 developer policy[2]. Specifically the part about IR Backwards Compatibility. The change from 3.9 to 4.0 is the following: - The textual format is not backwards compatible. We don’t change it too often, but there are no specific promises. - Additions and changes to the IR should be reflected

Hello, I am experiencing a number of 'Time moved backwards errors' such as: Mar 27 11:38:20 host-78-129-239-60 dovecot: imap-login: Time just moved backwards by 729 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards Mar 27 15:20:10 host-78-129-239-60 dovecot: Time just moved backwards by 4214 seconds. This might cause

How can I wrtie and calculate alpha and beta in the forward backward algorithm in R ? -- View this message in context: http://r.789695.n4.nabble.com/Forward-and-backward-algorithm-in-R-tp4648012.html Sent from the R help mailing list archive at Nabble.com.

> > > `SROA' is an early stage pass running at the very beginning of the > pipeline in `-O{1,2,3}'. Greg Bedwell's report from his DExTer tool > shows SROA on function as one of the major culprits of Debug Info > loss. > > The methodology I used is with the opt-bisect-limit option on clang, so it's not strictly the case that the results presented