search for: endy

Hello, Will there be support for big endiness machine or not? If not, would you please guide me how can I edit the library/libraries so they support such thing? I'm currently using opusfile, opuslib. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20130710/173d51a4/attachment.htm

I have a data set to be analyzed using to binary logistic regression. The data set is iin grouped form. My question is: how I can compute Hosmer-Lemeshow test and measures like sensitivity and specificity? Any suggestion will be greatly appreciated. Thank you Endy [[alternative HTML version deleted]]

I would like to make a suggestion. In the LiveIntervalAnalysis class, instead of numbering the instructions in the order in which basic blocks are stored in the machine function, use the df_ext_iterator. It will order the instruction according to the dominance tree (or it seems to be doing so). There are many advantages in doing this. One of them is that, once you traverse the dominance tree

On Thu, 21 Jun 2007, Fernando Magno Quintao Pereira wrote: > I would like to make a suggestion. In the LiveIntervalAnalysis class, > instead of numbering the instructions in the order in which basic blocks > are stored in the machine function, use the df_ext_iterator. It will order > the instruction according to the dominance tree (or it seems to be doing > so). There are many

Hi to every body. I would like assistance on how to implement the log-log link function for binary response. Is there any package that implements it? Many thanks Endy [[alternative HTML version deleted]]

Nice idea. Please also try using SmallPtrSet (with a sufficiently large size) instead of std::set for traversal after everything is working. Using std::set can really hurt compile time in case of large basic block numbers. Is there a way to dynamically adjust "SmallSize" based on number of basic blocks in the function? Evan On Jun 21, 2007, at 10:20 PM, Fernando Magno Quintao

Hello people, Since the invention of this storage called dbox, I have never quite gotten round to understanding it, nor getting to use it. It seems so strange to me and I must ask a few stupid questions about it. I use the MTA to deliver mail to Maildir, either in ~/Maildir or /some/path/%d/%n/Maildir. It has always beat me how dbox comes into play under such circumstances. From the wiki, I see

Hi there, Could somebody help me disect this legacy R script I inherited at work, I have two questions: 1. I've tried to upgrade our R version from 1.6.2 (yeah, I know), to R 2.0, but some of the lines in this script are not compatible with R 2.0, could someone help me figure out where the problem is? 2. the jpeg generated (attached) seems to be off on some of the data, is there a better way

...a set with SPSS i get a specific value. FlightNo Temp ThermalDisast 1 66 0 2 70 1 3 69 0 4 68 0 5 67 0 6 72 0 7 73 0 8 70 0 9 57 1 10 63 1 11 70 1 12 78 0 13 67 0 14 53 1 15 67 0 16 75 0 17 70 0 18 81 0 19 76 0 20 79 0 21 75 1 22 76 0 23 58 1 Any suggestions will greatly appreciated. With regards Endy [[alternative HTML version deleted]]

Hi Guys, We are trying to come up with Bi-Endian(neutral endiness) compiler using the LLVM. For a introduction . http://www.drdobbs.com/architecture-and-design/writing-a-bi-endian-compiler/240003090 Did someone from the group ,aware of such project . Thank you ~Umesh

Jean-Marc, It appears that since testcelt reads a WAVE file from disck and passes the data directly to celt_encode, so that celt_encode's "in" buffer must be expecting little-endian formatted packets. Is this correct? Is there endiness switch somewhere? Thx MikeH -------------- next part -------------- An HTML attachment was scrubbed... URL:

Pass to --commands-from-file the name of a file containing customization commands in each line, as if they were specified as command line arguments. This eases the reuse of commands among different builder/customize/sysprep invocations. --- builder/cmdline.ml | 3 +- customize/customize_run.ml | 5 +++ generator/customize.ml | 98 ++++++++++++++++++++++++++++++++++++++++++++-- 3

Hi, Just my two cents: If I recall correctly, in some papers on the linear scan register allocation people described that they tried different orderings for instruction numbering, e.g. including DFS or based on the loop nesting levels, etc. There was no clear winner though. But let's see the numbers anyway. May be it really brings some improvements. -Roman Chris Lattner wrote: > On

This is just a straight refactoring. Various ad hoc string_* functions that appeared in Common_utils have been renamed and placed in the String.* namespace. The old vs "new" functions are: string_prefix -> String.is_prefix string_suffix -> String.is_suffix string_find -> String.find replace_str -> String.replace string_nsplit -> String.nsplit string_split

I managed to compile newlib with llvm-gcc yesterday. That is, the machine independent part is now basically done, and the syscall part contains no-op stubs provided by libgloss. I haven't tested the port yet, but since newlib has already been ported to many architectures, I would be pretty surprised if there were any major problems. A couple of things I noticed when configuring newlib for

Woah this is a good idea. I'd ask that alignment come in different bit sizes and endienesses so that we can add an alignment type to ELF types. I would love to review this and add it to llvm-objcopy. We have special functions to handle all of these 'zero' cases. Several other bits of code I've seen/written have to find maximum alignment and I'd imagine the mistake of not

I am using R on a Windows XP professional platform. The following code is part of a bigger one CODE press=function(y,x){ library(qpcR) models.press=numeric(0) cat("\n") dep=y print(dep) indep=log(x) print(indep) yfit=dep-PRESS(lm(dep~indep))[[2]] cat("\n yfit\n") print(yfit) yfit.orig=yfit presid=y-yfit.orig press=sum(presid^2)

Hide/prevent the use of bad string functions like String.lowercase. These are replaced by safe functions that won't break UTF-8 strings. Other miscellaneous refactoring. Rich.

I have been quietly working on a port of LLVM to Stratus VOS. The OS is always big endian (because customers need to migrate data to new hardware quickly and can't afford to convert). This entails presenting a big endian programming model no matter what the hardware does. We did this about 15 years ago with the Stratus compilers and GCC. We offered the GCC changes back to the

...reign_key => ''parent_id'', :after_add => :after_add_child, :before_remove => :before_remove_child belongs_to :parent, :class_name => ''Company'', :foreign_key => ''parent_id'' # something similar to :after_add above? end -- Endy -- Posted via http://www.ruby-forum.com/.