Disable ArrayTranslateAndTest support on Z for remote compilations

[dchopra001]

Signed-off-by: Dhruv Chopra Dhruv.C.Chopra@ibm.com

[fjeremic]

@dchopra001 can you put some details here for future reference as to what problem you encountered which warranted disabling this? Looking at Idiom Recognition I also see many other related queries [1]. Do we need to disable all of these under JITServer? I would assume all of them would require some kind of table which I assume is the thing we couldn't relocate. Some details would be helpful to identify if this is the case.

[1] https://github.com/eclipse/openj9/blob/ec5d412fb412107af9b187cc1660d3d05d8b2df6/runtime/compiler/optimizer/IdiomRecognition.cpp#L1036-L1042

[dchopra001]

@fjeremic The problem on Z, as you mentioned in your comment, is that we are generating instructions like TROT that cannot be relocated currently.

Ex in the arrayTranslateEvaluator on Z: https://github.com/eclipse/omr/blob/1b7d7ab032b622b79b7d2372a13d90a770de78fb/compiler/z/codegen/OMRTreeEvaluator.cpp#L10750-L10771

See #6926 for a similar PR that disables some of the other queries on Z. (In hindsight I should have grouped these two PRs together).

Looking at Idiom Recognition I also see many other related queries [1]. Do we need to disable all of these under JITServer?

Some of the queries you've listed in your comment are only used on X and Power. So we don't need to disable all of them. I saw at least one such query on X which would eventually map to a loop in PicBuilder code that would perform the translation. So I don't think x86 is generating these tables that need relocations. I can't comment on Power yet. However if they are then we will need to disable those as well.

[fjeremic]

This is going into the jitaas branch so testing is not needed and the change is contained. I'm comfortable merging this obvious fix.