Bug 26912 - 'null == null' fooling blank final analysis
Summary: 'null == null' fooling blank final analysis
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 98
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-21 17:48 EST by Philipe Mulet CLA
Modified: 2003-02-07 09:06 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2002-11-21 17:48:41 EST 
Build 2.1-M3

The following code should be rejected:

public class X {
	final int blank;
	{ 	if (null == null) { 	
			blank = 1;	
		}	
	}	
	X(){	// blank may not be initialized (since null==null cannot be 
inlined)
	}	
}
Comment 1 Philipe Mulet CLA 2002-11-22 17:04:40 EST 
Fixed along with changes to flow analysis.
Comment 2 David Audel CLA 2002-12-17 11:35:35 EST 
Bug still occur in 2.1 M4 candidate

reopen and change target milestone to M5
Comment 3 Philipe Mulet CLA 2002-12-17 14:45:25 EST 
Seems like we still inline null==null where we shouldn't.
Need to investigate. Not critical
Comment 4 Philipe Mulet CLA 2003-01-29 05:28:33 EST 
Fixed. Was positioning an optimizedConstant were it shouldn't.
Comment 5 David Audel CLA 2003-02-07 09:06:49 EST 
Verified.