Fixed some of the XLA tests for IBM's Power architecture

[npanpaliya]

On IBM Power, some of the XLA tests used to fail with error "no target available for host triple x86..".
So, the PR tries to fix it in a way that it works on Power as well as x86. Other platforms can add their cases in cpu_compiler.h for these tests to work for them.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[gbaned]

@npanpaliya Thank you for your contribution. Can you please sign CLA? Thanks!

[npanpaliya]

Being an IBM Contractor, I've previously committed to this repo with appropriate Corporate CLA. It's just that my email has been changed now from "nishidha@us.ibm.com" to "npanpa23@in.ibm.com".

[rthadur]

@npanpaliya you should sign with all the emails associated, thank you

[npanpaliya]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[npanpaliya]

@sanjoy and @joker-eph - Could you please review this PR?

[sanjoy]

Can you share if you're using XLA CPU on IBM Power? Please feel free to follow up over private email (sanjoy AT {my employer}.com).

Thanks!

[npanpaliya]

Can you share if you're using XLA CPU on IBM Power? Please feel free to follow up over private email (sanjoy AT {my employer}.com).

Thanks!

Yes.

[gbaned]

@npanpaliya Any update on this PR? Please. Thanks!

[npanpaliya]

@gbaned - I'm sorry for the delay. I've done the suggested changes. But due to some other high priority work, could not test and push those. I'll do it tomorrow for sure.

[npanpaliya]

I'm really sorry for not being able to push my changes which address the review comments. I've been facing the build failure since yesterday due to ruy update. The latest ruy version being used by TF doesn't work on Power.

[npanpaliya]

I've put a PR to fix ruy on Power. google/ruy#83
Once this is accepted and merged, I'll raise another PR to bump up the version of ruy to the one that has fix for Power.

[rthadur]

@npanpaliya can you please check build failures ?

[npanpaliya]

@rthadur - I've fixed the build error. Thanks!

[gbaned]

@npanpaliya Can you please address Ubuntu Sanity errors? Thanks!

[npanpaliya]

I've been looking at them but I don't really understand what is the problem now.

[npanpaliya]

I've fixed the BUILD files using bazel buildifier utility. Hopefully all checks should be fine now.

[rthadur]

Seems auto-merge is not happening but the changes are now committed so we can close this. Thank you for the PR.