Bug 138324 - 2 * local variable used before set
Summary: 2 * local variable used before set
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-08 08:46 UTC by David Binderman
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-12 00:38:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Binderman 2004-11-08 08:46:41 UTC
Description of problem:

I just tried to compile package xorg-x11-6.8.1-4 from 
Redhat Fedora Core 3 Test 3.

The compiler said

1.

intel_pixel.c(172): remark #592: variable "size" is used before its
value is set

The source code is

   if (!check_color(ctx, type, format, pack, pixels, size, pitch))
      return GL_FALSE;

Suggest init size before first use.

2.

../../../../../../extras/Mesa/src/mesa/tnl_dd/t_dd_dmatmp.h(705):
remark #592: variable "currentsz" is used before its value is set

The source code is

      currentsz -= currentsz & 1;

Suggest init currentsz before first use.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mike A. Harris 2004-11-12 00:38:16 UTC
The problem reported here is only a cosmetic issue,
not a real problem with runtime consequences.  A similar issue
was previously reported in the Radeon driver.  The problematic
argument wasn't used at all in the Radeon driver, and I assume
isn't used in the Intel driver either, but X.Org can sort that
out.

If recompiling the xorg-x11 package, if you encounter any
compiler warnings or errors, please report them directly to
X.Org via the freedesktop.org bugzilla in the "xorg" component.

Setting status to WONTFIX, as this is a cosmetic upstream
issue.


Note You need to log in before you can comment on or make changes to this bug.