Bug 24825 - Standard runtime methods that are known to not return null should not trigger null checks.
Standard runtime methods that are known to not return null should not trigger...
Status: NEW
Product: gcc
Classification: Unclassified
Component: java
4.1.0
: P3 enhancement
: ---
Assigned To: Not yet assigned to anyone
: missed-optimization
Depends on: 20318
Blocks: 58689
  Show dependency treegraph
 
Reported: 2005-11-12 20:55 UTC by David Daney
Modified: 2013-10-11 12:19 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2006-02-13 03:43:47


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Daney 2005-11-12 20:55:52 UTC
As pointed out in this thread:

http://gcc.gnu.org/ml/java/2005-11/msg00124.html

Once we have the capability to annotate methods as returning 'not null', we have a win if standard runtime methods are so annotated as appropiate.
Comment 1 Andrew Pinski 2005-11-12 22:14:44 UTC
Confirmed, this one is harder than the new operator.
Comment 2 Andrew Pinski 2005-11-13 00:16:04 UTC
The way we can mark the function/function type is in build_method_invocation,
we have to change how BUILD_APPEND calls build_method_invocation and add a new argument or something like that (we build the real call expression later on).