On 10/21/2014 08:26 PM, Jeff Law wrote:
* optabs.c (emit_indirect_jump): Test HAVE_indirect_jump and emit a sorry if necessary.So doesn't this imply no hot-cold partitioning since we use indirect jumps to get across the partition? Similarly doesn't this imply other missing features (setjmp/longjmp, nonlocal gotos, computed jumps?
Pretty much yes to all.
Do you need some mechanism to ensure that hot/cold partitioning isn't enabled?
I guess I could clear flag_reorder_blocks_and_partition in nvptx_option_override. The problem hasn't come up so far.
Do you need some kind of message specific to the other features, or are we going to assume that the user will map from the indirect jump message back to the use of setjmp/longjmp or something similar?
I have some sorry calls in things like a dummy nonlocal_goto pattern. It doesn't quite manage to catch everything without an ICE yet though.
How are switches implemented (if at all)?
Comparison tree as you'd generate for small switches on all other targets. Bernd
