Closed
Bug 625610
Opened 13 years ago
Closed 10 years ago
nanojit: improve LIR checking to catch incorrect purity/AccSet annotations on native functions
Categories
(Core Graveyard :: Nanojit, defect)
Core Graveyard
Nanojit
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: n.nethercote, Unassigned)
Details
Bug 625333 is a scary example of what can happen if a functions purity/AccSet annotations are wrong. I want to improve the LIR checker to try to catch some incorrect annotations. For this particular example, if a function has an outparam that is allocp'd and it's marked as pure/ACCSET_NONE, that's extremely suspicious and very likely a bug. Any other suggestions for additional checks along these lines would be welcome. If a supposedly-pure function is passed a pointer to an int, double or boolean, that seems suspicious too.
Reporter | ||
Updated•13 years ago
|
Assignee: nnethercote → nobody
Status: ASSIGNED → NEW
Assignee | ||
Updated•10 years ago
|
Product: Core → Core Graveyard
Reporter | ||
Comment 1•10 years ago
|
||
Nanojit has been dead for several years. Its Bugzilla component has been moved to the graveyard (bug 984276). I checked all the open bugs. They're all uninteresting, so I'm WONTFIXing them all. Apologies for the bugspam.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•