Closed
Bug 726246
Opened 14 years ago
Closed 13 years ago
GCC 4.6 build warning: nsSVGFilters.cpp:3794:21: warning: variable 'yExt' set but not used [-Wunused-but-set-variable]
Categories
(Core :: SVG, defect)
Core
SVG
Tracking
()
RESOLVED
FIXED
People
(Reporter: dholbert, Assigned: froydnj)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
2.64 KB,
patch
|
Details | Diff | Splinter Review |
nsSVGFilters.cpp: In member function 'virtual nsresult nsSVGFEMorphologyElement::Filter(nsSVGFilterInstance*, const nsTArray<const nsSVGFE::Image*>&, const nsSVGFE::Image*, const nsIntRect&)':
nsSVGFilters.cpp:3794:21: warning: variable 'yExt' set but not used [-Wunused-but-set-variable]
This variable is mentioned 3 times:
> 3794 PRUint32 xExt[4], yExt[4]; // X, Y indices of RGBA extrema
[...]
> 3833 yExt[i] = y1;
[...]
> 3848 yExt[i] = y1;
Each of those lines simply set the value -- as the warning says, we never actually use the values in yExt. So (unless that's a problem) we can just drop it.
![]() |
Assignee | |
Comment 1•13 years ago
|
||
If it's not used, let's just remove it.
Comment 2•13 years ago
|
||
the comment needs updating since you've only got the X extrema now
![]() |
||
Comment 3•13 years ago
|
||
I'm going to get to this tomorrow - I just want to check through the spec on this filter and understand if we should be using these values somehow.
Alternatively, Robert, if you know this part of the spec and know that we don't need them, feel free to r+.
Comment 4•13 years ago
|
||
The values are used to optimise the calculations by storing values that we can use later. I haven't looked really closely at the code to see whether the yExt values that we're caching could be used to optimise the calculation further though.
There's nothing in the spec about this it's all our implementation.
Comment 5•13 years ago
|
||
Comment on attachment 597096 [details] [diff] [review]
patch
This bit was solved as part of 711043.
Attachment #597096 -
Flags: review?(jwatt)
Updated•13 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•13 years ago
|
Depends on: CVE-2013-1693
You need to log in
before you can comment on or make changes to this bug.
Description
•