search for: intervent

libswfdec/Makefile.am | 2 libswfdec/swfdec_as_strings.c | 2 libswfdec/swfdec_as_types.c | 6 + libswfdec/swfdec_interval.c | 184 ++++++++++++++++++++++++++++++++++++++++++ libswfdec/swfdec_interval.h | 78 +++++++++++++++++ libswfdec/swfdec_player.c | 2 libswfdec/swfdec_player_as.c | 178 ++++++++++------------------------------ 7 files changed, 320

Guys. I have an issue with a te110p card and also some tdm04b cards on the same system: Zttest returns this for the tdm04b cards: [root@mollendo ~]# /usr/src/zaptel-1.2.4/zttest 38 -v Opened pseudo zap interface, measuring accuracy... 8192 samples in 8191 sample intervals 99.987793% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples

Hi, I wrote a Function pass that requires the IntervalPartition pass in order to obtain the set of intervals for every function: virtual void getAnalysisUsage(AnalysisUsage &AU) const { AU.addRequired<IntervalPartition>(); } and get a handle to it in the runOnFunction method of my CustomPass: bool CustomPass::runOnFunction(Function& F) { IntervalPartition& iPart =

Dear All,   #I have the following code   Dose<-1000 Tinf <-0.5 INTERVAL <-8 TIME8 <-matrix(c((0*INTERVAL):(1*INTERVAL))) TIME7 <-matrix(c((0*INTERVAL):(2*INTERVAL))) TIME6 <-matrix(c((0*INTERVAL):(3*INTERVAL))) TIME5 <-matrix(c((0*INTERVAL):(4*INTERVAL))) TIME4 <-matrix(c((0*INTERVAL):(5*INTERVAL))) TIME3 <-matrix(c((0*INTERVAL):(6*INTERVAL))) TIME2

On Monday 06 August 2007 12:15, Anton Vayvod wrote: > Spill intervals must be precolored because they can't be spilled once more. > They are the shortest intervals precisely over each def/use of the original > interval. That is why they also have their weights set to #INF. Yes, that's true. But I wonder if we shouldn't be smarter about which register we pick to color it.

On 8/7/07, David Greene <dag at cray.com> wrote: > > On Monday 06 August 2007 12:15, Anton Vayvod wrote: > > > Spill intervals must be precolored because they can't be spilled once > more. > > They are the shortest intervals precisely over each def/use of the > original > > interval. That is why they also have their weights set to #INF. > > Yes,

---1149173172-1804289383-983267779=:26068 Content-Type: TEXT/plain; charset=us-ascii Hello, and a big thank you for providing R! Please find attached a diff for coplot which you may want to consider for the next release. The diff is against R 1.2.2. The reasons for this patch are: 1. The boxes of coplot did not align very well with the panel graphs if applied to a factor 2. Putting the

Dear r-users,   Originally my data is in notepad.  I use data.frame(...) to convert the data into columns but it has no header.  The data below is what I got in R.  I would like to extract these data:   19710629        39.3  19701126  19720629        33.8  19720517 ... when I use data2_30min[1, cbind(1,3,5)] command the result is NULL.   Then I tried data2_30min[1], it gives me the whole set of

Hi, I got selected for beta testing SW:TOR and managed to get the installer to work on wine but it keeps crashing when I try with the launcher. It opens for a smidgen then crashes. Here's all the script I get; fixme:iphlpapi:NotifyAddrChange (Handle 0x32e604, overlapped 0x8f8d58): stub fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported fixme:winsock:WSALookupServiceBeginW (0x32e628

I am trying to optimize some code to take advantage of R loop-avoiding capabilities when working on vectors/arrays that contain time intervals. The calculation involves adding (for each time interval) the time portion (of events defined by their start and end times) that elapsed during time intervals. Any advice on how to improve this code. I searched the email archive and looked at the MASS

On Feb 20, 2008, at 12:25 PM, David Greene wrote: > On Wednesday 20 February 2008 14:14, David Greene wrote: > >> I discovered this through an assert I put into some of my own >> code. I want >> to know if that assert is bogus or if there's a bug here. > > A little more information: the assert checks that after coalescing > two nodes, > all subregister

Hello, Thanks in advance for any help! How do I pass an unknown number of objects into the "..." (dot dot dot) parameter? Put another way, is there some standard way to pass multiple objects into "..." to "fool" the function into thinking the objects are passed in separately/explicitly with common separation (like "x,y,z" when x, y and z are objects to be

On Wednesday 20 February 2008 14:14, David Greene wrote: > I discovered this through an assert I put into some of my own code. I want > to know if that assert is bogus or if there's a bug here. A little more information: the assert checks that after coalescing two nodes, all subregister live intervals for the register coaelsced to now interfere with whatever the eliminated live

On Tuesday 07 August 2007 05:00, Anton Vayvod wrote: > > Yes, that's true. But I wonder if we shouldn't be smarter about which > > register we pick to color it. In Bill W's implementation, it was > > essentially random. What was your solution to this? > > I allocated spill intervals at the beginning of each iteration so all the > rest intervals (except of

hi, i noticed that se.fit from predict.lm is the same whether interval="conf" or interval="pred". it is not clear to me from ?predict.lm whether this is intended or not. i suggest that se.fit should match the type of interval requested, if interval is specified. suggested change in lm.R line 700 if(se.fit || interval != "none") se <- sqrt(ip) to if(se.fit

Hi all I have a list of multiple datframes with the same column headers. The last column in each datframe contains a vector of "Interval" class after I have produced this column using "lubridate" package. I needed to convert my list of dataframes to be in a single dataframe for further analysis. I did this using the following syntax : SingleDataframe <- ldply

Dear r-users,   I have saved data in word pad.  I would like to extract certain part of data only, for example   19710629 080000(PARTIAL) 39.3 at interval beginning 19701126 010326 19720629 080000(PARTIAL) 33.8 at interval beginning 19720517 144507 19730629 080000(PARTIAL) 32.2 at interval beginning 19720910 135747   and so on...   The original data set are given below:      

Hi Chris, Thanks for the reply. I am actually interested in using the Intervals Analysis mainly to be able to do Region based analysis. In fact, I found that the way Intervals are defined mirror exactly the definition of a Region in the second edition of the Dragon Book (Section 9.7 on Region-Based Analysis), so it will be great if the Intervals related code still lives on in LLVM :). I found

Hi, David. Spill intervals must be precolored because they can't be spilled once more. They are the shortest intervals precisely over each def/use of the original interval. That is why they also have their weights set to #INF. Imagine that on a second iteration allocation algorithm figures out that some spilled interval can't be assigned a physical register. Allocator can't spill it

On Aug 27, 2008, at 1:35 PM, Prakash Prabhu wrote: > Hi, > > I wrote a Function pass that requires the IntervalPartition pass in > order to obtain the set of intervals for every function: > > However when i access the intervals vector for a particular call of > runOnFunction, it seems that alll intervals computed for the earlier > functions are still in the > vector. To