Fixed bug #15 SDL_blit_A.mmx-speed.patch.txt -- Speed improvements and a bugfix for the current GCC inline mmx asm code: - Changed some ops and removed some resulting useless ones. - Added some instruction parallelism (some gain) The resulting speed on my Xeon improved upto 35% depending on the function (measured in fps). - Fixed a bug where BlitRGBtoRGBSurfaceAlphaMMX() was setting the alpha component on the destination surfaces (to opaque-alpha) even when the surface had none. SDL_blit_A.mmx-msvc.patch.txt -- MSVC mmx intrinsics version of the same GCC asm code. MSVC compiler tries to parallelize the code and to avoid register stalls, but does not always do a very good job. Per-surface blending MSVC functions run quite a bit faster than their pure-asm counterparts (upto 55% faster for 16bit ones), but the per-pixel blending runs somewhat slower than asm. - BlitRGBtoRGBSurfaceAlphaMMX and BlitRGBtoRGBPixelAlphaMMX (and all variants) can now also handle formats other than (A)RGB8888. Formats like RGBA8888 and some quite exotic ones are allowed -- like RAGB8888, or actually anything having channels aligned on 8bit boundary and full 8bit alpha (for per-pixel alpha blending). The performance cost of this change is virtually 0 for per-surface alpha blending (no extra ops inside the loop) and a single non-MMX op inside the loop for per-pixel blending. In testing, the per-pixel alpha blending takes a ~2% performance hit, but it still runs much faster than the current code in CVS. If necessary, a separate function with this functionality can be made. This code requires Processor Pack for VC6.

.TH "SDL_VideoInfo" "3" "Tue 11 Sep 2001, 23:01" "SDL" "SDL API Reference" 
.SH "NAME"
SDL_VideoInfo\- Video Target information
.SH "STRUCTURE DEFINITION"
.PP
.nf
\f(CWtypedef struct{
  Uint32 hw_available:1;
  Uint32 wm_available:1;
  Uint32 blit_hw:1;
  Uint32 blit_hw_CC:1;
  Uint32 blit_hw_A:1;
  Uint32 blit_sw:1;
  Uint32 blit_sw_CC:1;
  Uint32 blit_sw_A:1;
  Uint32 blit_fill;
  Uint32 video_mem;
  SDL_PixelFormat *vfmt;
} SDL_VideoInfo;\fR
.fi
.PP
.SH "STRUCTURE DATA"
.TP 20
\fBhw_available\fR
Is it possible to create hardware surfaces?
.TP 20
\fBwm_available\fR
Is there a window manager available
.TP 20
\fBblit_hw\fR
Are hardware to hardware blits accelerated?
.TP 20
\fBblit_hw_CC\fR
Are hardware to hardware colorkey blits accelerated?
.TP 20
\fBblit_hw_A\fR
Are hardware to hardware alpha blits accelerated?
.TP 20
\fBblit_sw\fR
Are software to hardware blits accelerated?
.TP 20
\fBblit_sw_CC\fR
Are software to hardware colorkey blits accelerated?
.TP 20
\fBblit_sw_A\fR
Are software to hardware alpha blits accelerated?
.TP 20
\fBblit_fill\fR
Are color fills accelerated?
.TP 20
\fBvideo_mem\fR
Total amount of video memory in Kilobytes
.TP 20
\fBvfmt\fR
\fIPixel format\fR of the video device
.SH "DESCRIPTION"
.PP
This (read-only) structure is returned by \fI\fBSDL_GetVideoInfo\fP\fR\&. It contains information on either the \&'best\&' available mode (if called before \fI\fBSDL_SetVideoMode\fP\fR) or the current video mode\&.
.SH "SEE ALSO"
.PP
\fI\fBSDL_PixelFormat\fR\fR, \fI\fBSDL_GetVideoInfo\fP\fR
...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:01