comparison src/share/vm/opto/matcher.hpp @ 2008:2f644f85485d

6961690: load oops from constant table on SPARC Summary: oops should be loaded from the constant table of an nmethod instead of materializing them with a long code sequence. Reviewed-by: never, kvn
author twisti
date Fri, 03 Dec 2010 01:34:31 -0800
parents f95d63e2154a
children 7e88bdae86ec
comparison
equal deleted inserted replaced
2007:5ddfcf4b079e 2008:2f644f85485d
363 // Should the Matcher clone shifts on addressing modes, expecting them to 363 // Should the Matcher clone shifts on addressing modes, expecting them to
364 // be subsumed into complex addressing expressions or compute them into 364 // be subsumed into complex addressing expressions or compute them into
365 // registers? True for Intel but false for most RISCs 365 // registers? True for Intel but false for most RISCs
366 static const bool clone_shift_expressions; 366 static const bool clone_shift_expressions;
367 367
368 // Should constant table entries be accessed with loads using
369 // absolute addressing? True for x86 but false for most RISCs.
370 static const bool constant_table_absolute_addressing;
371
368 static bool narrow_oop_use_complex_address(); 372 static bool narrow_oop_use_complex_address();
369 373
370 // Generate implicit null check for narrow oops if it can fold 374 // Generate implicit null check for narrow oops if it can fold
371 // into address expression (x64). 375 // into address expression (x64).
372 // 376 //