Closed
Bug 237191
Opened 22 years ago
Closed 18 years ago
Use NS_UNLIKELY for checking allocation failures
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: caillon, Unassigned)
Details
Attachments
(2 files)
|
600 bytes,
text/plain
|
Details | |
|
66.71 KB,
application/x-bzip2
|
bryner
:
review+
bryner
:
superreview+
|
Details |
I wrote a small perl script to find a few common allocation patterns and the
subsequent failure check, and wrap that check in an NS_UNLIKELY. There were a
few changes I had to make, but they are minimal. I've been using this build for
about an hour now without any problems.
| Reporter | ||
Comment 1•22 years ago
|
||
I ran this with `find -name "*.cpp" | xargs perl -i mkunlikely`
| Reporter | ||
Comment 2•22 years ago
|
||
| Reporter | ||
Updated•22 years ago
|
Attachment #143672 -
Flags: superreview?(bryner)
Attachment #143672 -
Flags: review?(bryner)
Comment 3•22 years ago
|
||
Comment on attachment 143672 [details]
Patch (tar.bz2)
r+sr=me based on my reading of the perl script and checking selected parts of
the patch.
Attachment #143672 -
Flags: superreview?(bryner)
Attachment #143672 -
Flags: superreview+
Attachment #143672 -
Flags: review?(bryner)
Attachment #143672 -
Flags: review+
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 4•20 years ago
|
||
Was this patch here ever checked in (does not seem so)? Probably a new patch is needed so if this should be checked in.
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•