search for: scast

That and the possibility of differently sized pointers made me hesitate to dive into implementing this. I guess nailing it down to be the platform equivalent of size_t would be sensible here. On Mon, Aug 9, 2010 at 1:37 PM, Eugene Toder <eltoder at gmail.com> wrote: > Small nitpick: size_t is not guaranteed to be large enough to hold a > pointer (only an array index, which can be

....frame$age edu <- data.frame$edu rural <- data.frame$rur rich <- data.frame$rich middle <- data.frame$middle poor <- data.frame$poor work <- data.frame$work jointfam <- data.frame$jfam contracep <- data.frame$contra hindu <- data.frame$hindu muslim <- data.frame$muslim scaste <- data.frame$scaste stribe <- data.frame$stribe obc <- data.frame$obc ucaste <- data.frame$ucaste N <- data.frame$dfsize indN <- data.frame$dfsize1 # INDICATOR FUNCTION THAT dfsize==alive nb <- data.frame$nboy ng <- data.frame$ngirl ncord1 <- data.frame$ncord1 # FIRST...

I looked through the "intp" thread. I don't really want to start that argument up again, but my immediate thought would be to create a new class of "picked-by-the-target" integer types (equivelents of size_t, intptr_t, etc...), and two new instructions, zcast and scast, which are only valid in the context of casting to / from integer types of unknown sizes. To begin with, most passes could probably ignore (or otherwise pass pass over) these instructions. The resolution of these types would only happen in the legalize phase in the SelectionDAG. Just my two cent...

Thanks for the info oddsock, I guess at the end of the day, if icecast was listing in scast and scast banned it then it would be a waste of time And they would ban the streams as soon as they find em being listed so we'll forget that idea ;-) Fred: http://www.steamcast.com/faq.php?p_id=#5 Regards. -----Original Message----- From: icecast-bounces@xiph.org [mailto:icecast-bounce...

Excellent results Oddsock, I'm surprised about the amount of free memory that is avalaible when using icecast instead of scast in high demand situations, impressive! Regards. -----Original Message----- From: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org] On Behalf Of oddsock Sent: 15 November 2005 4:52 AM To: icecast@xiph.org Subject: [Icecast] New icecast load test reports Just wanted to let everyone know...

...ally want to start that argument up again, but my immediate >>> > thought would be to create a new class of "picked-by-the-target" integer >>> > types (equivelents of size_t, intptr_t, etc...), and two new >>> > instructions, >>> > zcast and scast, which are only valid in the context of casting to / >>> > from >>> > integer types of unknown sizes.  To begin with, most passes could >>> > probably >>> > ignore (or otherwise pass pass over) these instructions.  The resolution >>> > of...