Bug 13319 - null pointer checks for CNI code
Summary: null pointer checks for CNI code
Status: NEW
Alias: None
Product: gcc
Classification: Unclassified
Component: java (show other bugs)
Version: 3.4.0
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: ABI
Depends on:
Blocks:
 
Reported: 2003-12-05 20:07 UTC by Tom Tromey
Modified: 2005-09-30 05:30 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2005-09-30 05:30:58


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Tromey 2003-12-05 20:07:08 UTC
Currently there's no way to enable null-pointer checking
for CNI code.  As part of the new ABI we should fix this.
The current plan is to wrap all pointer arguments in
a smart pointer class that, on platforms that require it,
will perform explicit null pointer checks.
Comment 1 Andrew Pinski 2003-12-05 20:30:56 UTC
Confimed (but really this is a C++ front-end issue, right?)
Comment 2 Tom Tromey 2003-12-05 20:32:21 UTC
No, it's really a gcj/libgcj issue.
Andrew submitted a g++ patch to add the checking there,
but it was rejected, so instead we have to do it by
hand in CNI, with gcj changes to match.