Re: Configure --with-mp=yes Who wants it?
Jay Cox wrote: Jon Winters wrote: Hi, Here is a screengrab if anyone is interested... [Jon Winters had reproduced #10595 with 1.1.25 distribution GRO] http://www.obscurasite.com/images/screengrabs/funky-tots.jpg Enjoy! EEK! I hope that isn't from the "fixed" version. I was hoping that it would fix that problem too. I still can't reproduce it here, but I only have the "fixed" version now. Jay Cox [EMAIL PROTECTED] Appears that your fix for #24188 also lays to rest #10595; I can reproduce neither phenomena this morning on the SGI and Linux machines with the new code and a complete rebuild. I think you bagged both. Congratulations. Interesting if Seth and Jon can confirm on #10595 and perhaps Thaddeus Parkinson [EMAIL PROTECTED] on his #24188. We should all keep an eye out for Tigert's thread dying message, as well. Be good, be well Garry
Re: Configure --with-mp=yes Who wants it?
"Garry R. Osgood" wrote: #10595 addenda snipped: see http://bugs.gnome.org/db/24/24188.html For the (speculative) 1.2 release: 1. Do we support this option (and fix the bugs)? 2. or do we shut down option --with-mp=yes ? Leaving the situation as-is I regard unacceptable for 1.2 release. Those with multiple CPU's will be naturally attracted to the switch, unlimiting the set of people affected in short order. What's not functional should not be offered, so either a fix or an option removal seems in order. How should cleanup proceed? Be good, be well Garry Osgood I just checked in a fix for #24188. I could never reproduce #10595, but I'm using a single processor machine. If those of you with MP machines could beat on it for a while and report back how it works for you I would appreciate it. I don't think we should remove MP mode quite yet, but I am rather biased. Jay Cox [EMAIL PROTECTED]
Re: Configure --with-mp=yes Who wants it?
I've got a multiprocessor machine. What exactly do I need to do to test this stuff? I haven't been following the entire thread. I should... ./configure --with-mp=yes Then do make and make install correct? Then what??? Just use gimp or do something specific to test. I think SMP optimization is important. The future of Gimp depends on it. we want Gimp to dominate on that new cube from Sony with 64 PSX2 processors. 8-) -- Jon Winters http://www.obscurasite.com/ "Everybody loves the GIMP!" http://www.gimp.org/
Configure --with-mp=yes Who wants it?
Hi, Brief investigations confirm that two bugs, #10595 [gimp-bug] Tile Rendering not working with erasure], reported by Seth Burgess [EMAIL PROTECTED] http://bugs.gnome.org/db/10/24188.html #24188 [gimp-bug] Tile Rendering not working with erasure[gimp-bug] image *still* not properly displayinglayer mode, reported by Thaddeus Parkinson [EMAIL PROTECTED] http://bugs.gnome.org/db/24/24188.html occur only when gimp is built with configure option --with-mp=yes. (multiprocessor support). #24188 substantially compromises Gimp functionality: In new images, layers with properties other than "Normal" or "Dissolve" become invisible. Seth Burgess wrote [in Re: Bug#10595: [gimp-bug] Tile Rendering not working with erasure] Yes, we did discuss that briefly... [At Berlin GimpCon - GRO] is this bug worth tracking down as it is a very limited set of people affected? Seth #10595 addenda snipped: see http://bugs.gnome.org/db/24/24188.html For the (speculative) 1.2 release: 1. Do we support this option (and fix the bugs)? 2. or do we shut down option --with-mp=yes ? Leaving the situation as-is I regard unacceptable for 1.2 release. Those with multiple CPU's will be naturally attracted to the switch, unlimiting the set of people affected in short order. What's not functional should not be offered, so either a fix or an option removal seems in order. How should cleanup proceed? Be good, be well Garry Osgood