RSS/Atom feed Twitter
Site is read-only, email is disabled

Status of MMX code in The GIMP

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

1 of 1 message available
Toggle history

Please log in to manage your subscriptions.

Status of MMX code in The GIMP Helvetix Victorinox 20 Jun 18:13
Helvetix Victorinox
2003-06-20 18:13:35 UTC (over 21 years ago)

Status of MMX code in The GIMP

Last Februrary, I volunteered to help with the GIMP MMX implemetation that had been languishing and had recently started to cause problems when building the current GIMP code.

This (http://oak.mysterious.org/~helvetix/practicum/gimp-composite.tgz) is release 0.0 of an extensible and customisable image compositing interface for the GIMP. This doesn't really provide any 'user visible' changes, other than the potential (and actual in this case) performance improvements.

I'd like to hear feedback.

What you get is this:

* A general mechanism for incorporating compositing functions based upon the compositing function and the pixel formats of the inputs and the outputs of the function.

* Generic implementations of the supported compositing functions as a foundation for further/future improvements.

* The general mechanism allows any compositing function implementation to be replaced by a different implementation. This is particularly useful in that one can write specialised implementation of some, many, or all of the compositing functions. These specialised implementations can be written to take advantage of special CPU instructions, such as VIS, AltiVec, MMX, and so forth, and special hardware acceleration that might be available.

Currently, I have an incipient set of functions implemented which use the MMX instruction set of the Pentium processor.

Helvetix