aboutsummaryrefslogtreecommitdiff
path: root/gcc/objc/THREADS.MACH
diff options
context:
space:
mode:
Diffstat (limited to 'gcc/objc/THREADS.MACH')
-rw-r--r--gcc/objc/THREADS.MACH23
1 files changed, 0 insertions, 23 deletions
diff --git a/gcc/objc/THREADS.MACH b/gcc/objc/THREADS.MACH
deleted file mode 100644
index 55de6637866..00000000000
--- a/gcc/objc/THREADS.MACH
+++ /dev/null
@@ -1,23 +0,0 @@
-This readme refers to the file thr-mach.c.
-
-Under mach, thread priorities are kinda strange-- any given thread has
-a MAXIMUM priority and a BASE priority. The BASE priority is the
-current priority of the thread and the MAXIMUM is the maximum possible
-priority the thread can assume. The developer can lower, but never
-raise the maximum priority.
-
-The gcc concept of thread priorities is that they run at one of three
-levels; interactive, background, and low.
-
-Under mach, this is translated to:
-
-interactive -- set priority to maximum
-background -- set priority to 2/3 of maximum
-low -- set priority to 1/3 of maximum
-
-This means that it is possible for a thread with the priority of
-interactive to actually run at a lower priority than another thread
-with a background, or even low, priority if the developer has modified
-the maximum priority.
-
-