Attachment 52056 Details for Bug 29151 – Patch 02 of 02 Compiler noise cleanups related to subpixel LCD changes

[patch] Patch 02 of 02 Compiler noise cleanups related to subpixel LCD changes

0002-compiler-noise-cleanups-related-to-subpixel-LCD-supp.patch (text/plain), 1.32 KB, created by Tom Callaway on 2011-10-06 13:01:55 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Tom Callaway

Created: 2011-10-06 13:01:55 UTC

Size: 1.32 KB

patch

obsolete

>From fdab25ce326cc0faf7d853a36394503a78141688 Mon Sep 17 00:00:00 2001
>From: "Tom \"spot\" Callaway" <tcallawa@redhat.com>
>Date: Thu, 6 Oct 2011 15:58:29 -0400
>Subject: [PATCH 2/2] compiler noise cleanups related to subpixel LCD support
>
>---
> src/xftglyphs.c |   10 +++-------
> 1 files changed, 3 insertions(+), 7 deletions(-)
>
>diff --git a/src/xftglyphs.c b/src/xftglyphs.c
>index 03d94ed..2639d12 100644
>--- a/src/xftglyphs.c
>+++ b/src/xftglyphs.c
>@@ -358,7 +358,7 @@ XftFontLoadGlyphs (Display	    *dpy,
>     unsigned char   bufLocal[4096];
>     unsigned char   *bufBitmap = bufLocal;
>     int		    bufSize = sizeof (bufLocal);
>-    int		    size, pitch;
>+    int		    size;
>     int		    width;
>     int		    height;
>     int		    left, right, top, bottom;
>@@ -572,7 +572,6 @@ XftFontLoadGlyphs (Display	    *dpy,
> 
> 	width = ftbit->width;
> 	height = ftbit->rows;
>-	pitch = (width+3) & ~3;
> 
> 	if (XftDebug() & XFT_DBG_GLYPH)
> 	{
>@@ -674,12 +673,9 @@ XftFontLoadGlyphs (Display	    *dpy,
> 		/* swap bits in each byte */
> 		if (BitmapBitOrder (dpy) != MSBFirst)
> 		{
>-		    unsigned char   *line;
>-		    unsigned char   c;
>-		    int		    i;
>+		    unsigned char   *line = (unsigned char*)bufBitmap;
>+		    int		    i = size;
> 
>-		    line = (unsigned char *) bufBitmap;
>-		    i = size;
> 		    while (i--)
> 		    {
> 			int c = *line;
>-- 
>1.7.6.4
>

Actions: View | Splinter Review

Attachments on bug 29151: 37182 | 52055 | 52056

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.