RISC-V: add native build spec

[janvrany]

This PR adds a RISC-V native build spec in order to (re) enable OMR CI for RISC-V using RISC-V hardware.
For details see #7530.

[AdamBrousseau]

jenkins build riscv

[AdamBrousseau]

Looks like the container is missing git. I commented in the Eclipse issue.

[AdamBrousseau]

jenkins build riscv

[janvrany]

jenkins build riscv

[AdamBrousseau]

@babsingh can you confirm if we need to change the alias code for riscv vs riscv_cross specs? Seems this is related to adding extra build or test options. Do we leave them both as riscv or should the old one be changed to riscv_cross?

[babsingh]

It makes sense to differentiate between the two variants, i.e., include both riscv and riscv_cross. Otherwise, we lose control over distinguishing between the two builds.

[janvrany]

jenkins build riscv

[janvrany]

@babsingh

It makes sense to differentiate between the two variants, i.e., include both riscv and riscv_cross. Otherwise, we lose control over distinguishing between the two builds.

So you suggest to do the following?

omr/buildenv/jenkins/omrbuild.groovy

Lines 163 to 164 in 62d4368

	'linux_riscv64_cross' : [
	'alias': 'riscv_cross',

and

omr/buildenv/jenkins/omrbuild.groovy

Lines 183 to 184 in 62d4368

	'linux_riscv64' : [
	'alias': 'riscv',

[babsingh]

Yes, just the aliases should differ for the two configurations. If you'd like, you can suggest shorter alias names.

[janvrany]

Looking at (failed) run 6 ( https://ci.eclipse.org/omr/job/PullRequest-linux_riscv64/6/console):

• TestJitBuilderAPIGenerator fails because of Rename deprecated Python unittest function assertRegexpMatches #7279, maybe I can come up with different solution (than Rename deprecated Python unittest function assertRegexpMatches #7279) that would work everywhere.
• porttest fails (wild-guessing) because of core file size limits.

I'll have another look next week.