[aarch64-port-dev ] Mixing of aarch64_c2 and default branch code

[Edward Nevill]

On Mon, 2013-08-12 at 09:50 +0100, Andrew Dinn wrote:

> This doesn't actually matter as far as building the C1/C2 variants goes
> because the C2 code (in aarch64.ad or generated from it) does not get
> included in the build process unless you configure either a tiered or a
> C2 build. However, it does make it a little easier for me to make
> changes which break C1. I don't know whether it is worth continuing with
> a separate aarch64_c2 branch given that the code bases are now
> effectively merged. Anyone have any opinions on this?

Hi Andrew,

Yes, I vote for merging to a single branch.

Can the jvm.cfg read

-client KNOWN
-server IGNORE

This is for the CI loop running jtreg. jtreg specifies -server on many of the tests.

For C2 this would need to be manually changed to -server KNOWN.

All the best,
Ed.