Re: [Paracomp-devel] Crash in pcSystemFinalize
Brought to you by:
shreekumar
|
From: Shree K. <shr...@hp...> - 2008-04-28 14:47:48
|
Hi Stefan On Mon, 2008-04-28 at 14:27 +0000, Stefan Eilemann wrote: > Me again, > > With the simple compositing test in Equalizer I now get a segmentation > fault in pcSystemFinalize: ... > > OS: Ubuntu 6.10 > HW: Opteron 248 > Can you do a build with "release=0" (to enable debug symbols) and post the stack trace ? That would help me a bit. > > I also get similar, disappointing performance results as on my Mac: > > PC: 15 images: 11.431 ms (1601.83 MB/s) > Eq: 15 images: 9.207 ms (1988.76 MB/s) I think the slower code is primarily a difference in compiler optimization behaviour. I haven't found a good solution for this right now. The following approach looks like a sufficient workaround -- I'll make a special case for the pixel formats you are using (Currently this is going through some template expansion and I don't know why the performance is different. Once the format is special cased the results will match - because they are basically the same code :-) I'll do this tomorrow and update you. > Do I have to configure something in order to use the opteron 'plugin'? > That's not needed for depth compositing, since there is no special code. For alpha blending, it will get used automatically (provided it's found in PC_LIBRARY_PATH/composite). HTH -- Shree |