search for: rietveld

...nl/discadmin/ ). We don't get access to this page which is necessary to pick up our new password, for broadcasting with nicecast 2) Someone changed the server type settings: What is the difference between icecast 1 and icecast 2 and which one is the most likely to use for us? Thanx, Hans Radio Rietveld -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20071205/fbeac3f0/attachment.htm>

...Output to other devices such as pdf is perfect. Possibly this reflects a different scaling being applied when points() or lines() are selected. One reason I found this is that I use a number of scripts in R to plot and multiplot data sets from x-ray and neutron powder diffraction analysis (and Rietveld fitting of this data in particularl). In these points() is used to plot the data and lines() to plot the refinement from the analysis. After upgrading I found these were misaligned. The example was created to mimic the problem. %%% Example follows: dtwoth <- seq(from=20,to=80,len=1024) dcou...

...db/jit.[ch] but I don't know how to get cvs diff to include them. 'cvs add' wants write access on the main server. Supposedly 'cvs diff -upN' will do it, but it's not working for me... Expect to hear back. >> And finally, the patch to LLVM is attached and uploaded to Rietveld: >> http://codereview.appspot.com/91042/show >> > > In general I'd like to see the ELF support separated from the main > interface. It makes any other platform support require a complete > refactor :) That's a goal I have for the summer. One dumb way to approach it...

...8) at ExecutionEngine.cpp:376 #6 0x00000000007eb665 in main (argc=3, argv=0x7fffffffe3d8, envp=0x7fffffffe3f8) at lli.cpp:205 (gdb) For reference, here is the corresponding patch against GDB: http://web.mit.edu/rnk/www/jit-patch.diff And finally, the patch to LLVM is attached and uploaded to Rietveld: http://codereview.appspot.com/91042/show I know this code is sketchy and preliminary, but it's useful for us, and I have plans to improve it: http://wiki.llvm.org/HowTo:_Tell_GDB_about_JITted_code Please review! Thanks, Reid -------------- next part -------------- A non-text attachment was...

...nyurl.com/37u84z4 > > ### regex_v8 ### > Mem max: 33596.000 -> 33828.000: 1.0069x larger > Usage over time: http://tinyurl.com/397hyfm > > ### richards ### > Mem max: 12760.000 -> 12680.000: 1.0063x smaller > Usage over time: http://tinyurl.com/25n3wkl > > ### rietveld ### > Mem max: 29008.000 -> 28636.000: 1.0130x smaller > Usage over time: http://tinyurl.com/25uu4x3 > > ### slowpickle ### > Mem max: 14096.000 -> 13804.000: 1.0212x smaller > Usage over time: http://tinyurl.com/2wzxmu2 > > ### slowspitfire ### > Mem max: 94292.0...

...84.000: 1.0212x smaller Usage over time: http://tinyurl.com/37u84z4 ### regex_v8 ### Mem max: 33596.000 -> 33828.000: 1.0069x larger Usage over time: http://tinyurl.com/397hyfm ### richards ### Mem max: 12760.000 -> 12680.000: 1.0063x smaller Usage over time: http://tinyurl.com/25n3wkl ### rietveld ### Mem max: 29008.000 -> 28636.000: 1.0130x smaller Usage over time: http://tinyurl.com/25uu4x3 ### slowpickle ### Mem max: 14096.000 -> 13804.000: 1.0212x smaller Usage over time: http://tinyurl.com/2wzxmu2 ### slowspitfire ### Mem max: 94292.000 -> 93992.000: 1.0032x smaller Usage ove...

On 2010-11-10 12:58, Renato Golin wrote: > In a nutshell, the design decisions should be communicated more > effectively, and a Wiki is a great place to start. Peer reviewers > should communicate via the Wiki, so patchers could learn and plan > before the next iteration and reduce the cost for everybody. You may consider using a review tool rather than (or in addition to)

On Wed, Jul 8, 2009 at 11:41 AM, Reid Kleckner<rnk at mit.edu> wrote: > Right now, GDB has no way to be told about JITed code.  I'm working on > adding such an interface, and the LLVM JIT would be the first client. Have you considered how this might be made to work for embedded targets where remote debugging is required? deep