File: include-signal.swift

package info (click to toggle)
swiftlang 6.1.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,791,532 kB
  • sloc: cpp: 9,901,743; ansic: 2,201,431; asm: 1,091,827; python: 308,252; objc: 82,166; f90: 80,126; lisp: 38,358; pascal: 25,559; sh: 20,429; ml: 5,058; perl: 4,745; makefile: 4,484; awk: 3,535; javascript: 3,018; xml: 918; fortran: 664; cs: 573; ruby: 396
file content (33 lines) | stat: -rw-r--r-- 1,256 bytes parent folder | download | duplicates (2)
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
// RUN: %target-typecheck-verify-swift -I %S/Inputs

// Some types such as pid_t that glibc defines are defined using the following
// construct:
//
// #ifndef __pid_t_defined
// typedef __pid_t pid_t;
// #define __pid_t_defined
// #endif
//
// glibc defines pid_t in this way in multiple header files, as required by
// POSIX (e.g. signal.h, unistd.h, and sys/types.h). A number of other types
// use the same construct (e.g. ssize_t, intptr_t, uid_t, gid_t).
//
// Because Swift does not set the -fmodules-local-submodule-visibility flag,
// the __pid_t_defined macro can leak from the first submodule that defines it
// into all submodules that follow.
//
// As a consequence, a C header file may fail to compile when imported into
// Swift, even though it compiles cleanly outside Swift with the same system
// headers.
//
// This is a regression test for a bug that was once present in SwiftGlibc
// module layout. Originally SwiftGlibc defined one submodule per header, and
// types such as pid_t were defined by the first module that encountered the
// ifndef construct.
//
// See https://forums.swift.org/t/problems-with-swiftglibc-and-proposed-fix/37594
// for further details.

// REQUIRES: OS=linux-gnu || OS=linux-android

import IncludeSignal