Conditionalize 'num_extra_inhabitants' in 64 bit platforms's tests

[augusto2112]

Quoting @tbkka: The number of extra inhabitants actually depends to some extent on the OS. Apple platforms reserve a 4GB "page zero" on 64 bit platforms in order to help detect 32/64 bit errors. [...] But Linux only reserves a 4K page zero, so there are only 4096 invalid pointer values.

This PR adds variables num_extra_inhabitants, num_extra_inhabitants_minus_1, num_extra_inhabitants_minus_2 and num_extra_inhabitants_minus_3, with the proper platform's values, and replaces the usages of those raw values by the variables.

It also enables the tests under Linux which are now working thanks to these changes and #32339.

[augusto2112]

@vedantk @adrian-prantl In this PR I only substituted the raw values by the new variables in the tests that are passing on Linux. I can also do that to the tests which are not passing. I think that'd be better, so we don't have 2 different ways to refer to the 64-bit num_extra_inhabitants inside the tests. Should I do that here?

[adrian-prantl]

If I understand your question correctly, I would prefer to update all tests at once, even the ones currently not running.

[augusto2112]

@adrian-prantl Ok, pushed!

[adrian-prantl]

@swift-ci smoke test

[adrian-prantl]

@swift-ci test

[swift-ci]

Build failed
Swift Test Linux Platform
Git Sha - ce80a1cb7d9100786b9d8d7e10da3542fecc36b8

[swift-ci]

Build failed
Swift Test OS X Platform
Git Sha - ce80a1cb7d9100786b9d8d7e10da3542fecc36b8

[vedantk]

@swift-ci smoke test

[vedantk]

@swift-ci smoke test

[vedantk]

@swift-ci smoke test

[augusto2112]

It looks like it failed to build SwiftPM:

/home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/branch-master/swiftpm/Tests/PackageLoadingTests/PD4LoadingTests.swift:304: error: PackageDescription4LoadingTests.testUnavailableAPIs : XCTAssertTrue failed - /home/buildnode/jenkins/workspace/swift-PR-Linux-smoke-test/branch-master/tmp/TemporaryFile.zaq0aq.swift:5:9: error: 'package(url:version:)' is unavailable: use package(url:_:) with the .exact(Version) initializer instead

Should I just rebase on top of current master?

[tbkka]

Should I just rebase on top of current master?

You don't necessarily need to rebase. You could also just merge current master.

Either way, it's a good idea to do one or the other every week or so to make sure that your work is correctly tracking ongoing changes there. That will make it easier to merge your work back into master when it's ready.

[vedantk]

@swift-ci smoke test

[vedantk]

@swift-ci smoke test OS X platform