File: allocator_sanity.swift

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (35 lines) | stat: -rw-r--r-- 1,245 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
// RUN: %target-run-simple-swiftgyb

// REQUIRES: executable_test
// UNSUPPORTED: use_os_stdlib
// UNSUPPORTED: back_deployment_runtime

import StdlibUnittest

var AllocationsTestSuite = TestSuite("Allocations")

AllocationsTestSuite.test("absurd.allocation.misaligned") {
  expectCrashLater()
  let mustFail = UnsafeMutableRawPointer.allocate(byteCount: 1024,
                                                  alignment: 19)
  expectUnreachable()
  _ = mustFail
}

AllocationsTestSuite.test("absurd.allocation.gargantuan") {
  expectCrashLater()
  // There is a chance that we'll actually be able to allocate Int.max bytes on
  // 32-bit platforms, since they often have 4GB address spaces and Int.max is
  // 2GB minus one byte. Allocate twice to ensure failure. That will (attempt
  // to) allocate 4GB minus two bytes, and we'll definitely have more than two
  // bytes of other stuff in the process.
  let mustFail = UnsafeMutableRawPointer.allocate(byteCount: Int.max,
                                                  alignment: 0)
  let mustFail2 = UnsafeMutableRawPointer.allocate(byteCount: Int.max,
                                                   alignment: 0)
  expectUnreachable()
  _ = mustFail
  _ = mustFail2
}

runAllTests()