search for: nowish

...nzhou, On Sat, Aug 14, 2010 at 8:25 PM, Jianzhou Zhao <jianzhou at seas.upenn.edu> wrote: > Hi, > > Does 2.8 release plan to change anything in Ocaml bindings? > http://llvm.org/docs/ReleaseNotes.html#whatsnew does not list any > relevant features. I usually wait until around nowish before a release to sync llvm-c and the ocaml bindings. I'll start the process. Is there anything in particular you are looking for? I'm happy to integrate patches for you. > 2.7 added 'operand' that can access each operand from a value. >  external operand : llvalue -> i...

...ressions as quickly as possible, so please report any issues to this list and/or the freedesktop bugzilla. There's two areas that didn't get "properly" ported over, that is PM-related things and modesetting. I'll be handling the modesetting and clk/volt reworks starting from nowish (in between fixing regressions), and I suspect Martin will handle the rest of the PM bits (therm and fanctrl) since he knows the design he's going for there. One thing to note is that some kernel module options have changed now, the more important ones are: nouveau.vbios=<blah> -> no...

Hi, Does 2.8 release plan to change anything in Ocaml bindings? http://llvm.org/docs/ReleaseNotes.html#whatsnew does not list any relevant features. 2.7 added 'operand' that can access each operand from a value. external operand : llvalue -> int -> llvalue = "llvm_operand" Does this binding also expose a primitive to return how many operands a given value has? I need

Had a nasty memory leak that was seriously slowing down the browser and eating up a couple megabytes every reload. I was using: $$(''.dyntable'').each(function(elm) { new DynTable(elm) }); To set up my behavior, but discovered that just running: $$(''.dyntable''); Caused the memory leak all by itself. The fix I found for it was to change Element.extend to a