This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Why does GCJ generate so many explicit checks for null pointers?
- From: Tom Tromey <tromey at redhat dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: David Daney <ddaney at avtrex dot com>, <java at gcc dot gnu dot org>
- Date: 29 Jul 2003 09:03:00 -0600
- Subject: Re: Why does GCJ generate so many explicit checks for null pointers?
- References: <Pine.LNX.4.44.0307291058150.10041-100000@ops2.one-point.com>
- Reply-to: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
Jeff> But malloc can return NULL, right? From what I understand the
Jeff> malloc attribute is a hint for alias analysis, and doesn't say
Jeff> anything about the null-ness of its return value.
Duh on me, you're right.
Maybe we need some new internal attribute.
This sounds like something to put in bugzilla.
Tom