search for: sucessor

Displaying 9 results from an estimated 9 matches for "sucessor".

Did you mean: successor
2008 Dec 23
2
Exide NetUPS SE (aka Powerware 5119 etc)
...o http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was previously also known as Fiskars PowerRite Max and before that Fiskars PowerServer 10. The current Powerware models (e.g. the sucessor 5125) are sold under the name Eaton Powerware. The NUT UPS hardware compatibility list does list Compaq R3000h, Deltec PowerRite Pro II, Exide NetUPS SE, Fiskars PowerRite Max, Fiskars PowerServer 10, and Powerware 5119. They are all said to be compatible with the genericups driver, type 15, excep...
2008 Dec 23
2
Exide NetUPS SE (aka Powerware 5119 etc)
...o http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was previously also known as Fiskars PowerRite Max and before that Fiskars PowerServer 10. The current Powerware models (e.g. the sucessor 5125) are sold under the name Eaton Powerware. The NUT UPS hardware compatibility list does list Compaq R3000h, Deltec PowerRite Pro II, Exide NetUPS SE, Fiskars PowerRite Max, Fiskars PowerServer 10, and Powerware 5119. They are all said to be compatible with the genericups driver, type 15, excep...
2011 Jun 04
3
[LLVMdev] [llvm-commits] Branch Probability
...Note that profiled edge weights are *not* raw sample counts provided by a profiler. The weights are adjusted to express branch probability when compared with other weights from a predecessor block's successor list. The same probability can be expressed multiple ways by scaling the values of all sucessor edges. Successor edge weights need not sum to any particular value. Edge weights have no meaning when compared across different branches. The details of this representation aren't important because it is not the primary interface used by the optimizer. In fact, we could easily support new meta...
2007 Sep 18
0
Support .cda as input files
...corresponding standard for laying out the filesystem within the available storage (ISO 9660). There is also the fact that a CD player was expected to implemented in hardware or with a very simple processor so the format had to be simple. By the time DVD was being designed (and it's subequent sucessors to be) CD-ROM has been around for a while and DVD players were expected to have internal software that could cope with the complexity of working with a filesystem on the disk rather than a simple data stream. Steve.
2007 Sep 14
5
Support .cda as input files
does anybody know why dvd use files for audio and video but audio cd's not? What could be the reason for this? e.g. they could make a file for each track and just put them on an audio cd and make cd players compatible with this format. So for me it has always been a mystery why audio cd's work this way. does anybody knows if super audio cd's still work the same as normal ones?
2010 Dec 01
0
[LLVMdev] Alternative exception handling proposal
...for eh.exception, in fact > the same code could be used for both. > > Currently when the code generators see an invoke, they rummage around in > the landing pad looking for an eh.selector call so they can extract the > catch info (and if it doesn't find one, it tries to look in sucessor blocks > because loop passes like to move eh.selector there...). Now they don't have > to rummage because the needed information is directly attached to the invoke. > See my point above about the eh.selector call. > Inlining > -------- > > Many a plausible seeming excep...
2010 Dec 01
8
[LLVMdev] Alternative exception handling proposal
...red, like it does already for eh.exception, in fact the same code could be used for both. Currently when the code generators see an invoke, they rummage around in the landing pad looking for an eh.selector call so they can extract the catch info (and if it doesn't find one, it tries to look in sucessor blocks because loop passes like to move eh.selector there...). Now they don't have to rummage because the needed information is directly attached to the invoke. The eh.set.selector and eh.set.exception intrinsics --------------------------------------------------- These new intrinsics can be...
2019 Feb 09
1
[RFC] Adding thread group semantics to LangRef (motivated by GPUs)
...difference > between instructions in the same BB before and after a convergence > instrinsic? > The way I was thinking, we'd allow the merge instruction anywhere in a basic block. Otherwise, we'd have to allow for cases where there's a trivial edge from a basic block with one sucessor to a block with one predecessor that can't be eliminated. For example, in the single-break case mentioned earlier: while (true) { if (...) { ballot(); // should be executed before re-converging. break; } } ballot(); // should be executed after re-converging With a merg...
2019 Feb 01
2
[RFC] Adding thread group semantics to LangRef (motivated by GPUs)
On 31.01.19 15:59, Jan Sjodin wrote: >> >  Any transform that re-arranges control flow would potentially have to >> >  know about the properties of ballot(), and the rules with respect to >> >  the CFG (and maybe consider the target) to know where to insert the >> >  intrinsics. > >> But the same is true for basically any approach to handling this. In