Add x prefix to v850e case for handling --with-cpu=v850e.
[official-gcc.git] / gcc / ada / g-tasloc.ads
blob7b09d45d5d5ace8407607a7ebe74f1d753f7c936
1 ------------------------------------------------------------------------------
2 -- --
3 -- GNAT RUN-TIME COMPONENTS --
4 -- --
5 -- G N A T . T A S K _ L O C K --
6 -- --
7 -- S p e c --
8 -- --
9 -- --
10 -- Copyright (C) 1998-2001 Ada Core Technologies, Inc. --
11 -- --
12 -- GNAT is free software; you can redistribute it and/or modify it under --
13 -- terms of the GNU General Public License as published by the Free Soft- --
14 -- ware Foundation; either version 2, or (at your option) any later ver- --
15 -- sion. GNAT is distributed in the hope that it will be useful, but WITH- --
16 -- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY --
17 -- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License --
18 -- for more details. You should have received a copy of the GNU General --
19 -- Public License distributed with GNAT; see file COPYING. If not, write --
20 -- to the Free Software Foundation, 59 Temple Place - Suite 330, Boston, --
21 -- MA 02111-1307, USA. --
22 -- --
23 -- As a special exception, if other files instantiate generics from this --
24 -- unit, or you link this unit with other files to produce an executable, --
25 -- this unit does not by itself cause the resulting executable to be --
26 -- covered by the GNU General Public License. This exception does not --
27 -- however invalidate any other reasons why the executable file might be --
28 -- covered by the GNU Public License. --
29 -- --
30 -- GNAT is maintained by Ada Core Technologies Inc (http://www.gnat.com). --
31 -- --
32 ------------------------------------------------------------------------------
34 -- Simple task lock and unlock routines
36 -- A small package containing a task lock and unlock routines for creating
37 -- a critical region. The lock involved is a global lock, shared by all
38 -- tasks, and by all calls to these routines, so these routines should be
39 -- used with care to avoid unnecessary reduction of concurrency.
41 -- These routines may be used in a non-tasking program, and in that case
42 -- they have no effect (they do NOT cause the tasking runtime to be loaded).
44 package GNAT.Task_Lock is
45 pragma Elaborate_Body (Task_Lock);
47 procedure Lock;
48 pragma Inline (Lock);
49 -- Acquires the global lock, starts the execution of a critical region
50 -- which no other task can enter until the locking task calls Unlock
52 procedure Unlock;
53 pragma Inline (Unlock);
54 -- Releases the global lock, allowing another task to successfully
55 -- complete a Lock operation. Terminates the critical region.
57 -- The recommended protocol for using these two procedures is as
58 -- follows:
60 -- Locked_Processing : begin
61 -- Lock;
62 -- ...
63 -- TSL.Unlock;
65 -- exception
66 -- when others =>
67 -- Unlock;
68 -- raise;
69 -- end Locked_Processing;
71 -- This ensures that the lock is not left set if an exception is raised
72 -- explicitly or implicitly during the critical locked region.
74 -- Note on multiple calls to Lock: It is permissible to call Lock
75 -- more than once with no intervening Unlock from a single task,
76 -- and the lock will not be released until the corresponding number
77 -- of Unlock operations has been performed. For example:
79 -- GNAT.Task_Lock.Lock; -- acquires lock
80 -- GNAT.Task_Lock.Lock; -- no effect
81 -- GNAT.Task_Lock.Lock; -- no effect
82 -- GNAT.Task_Lock.Unlock; -- no effect
83 -- GNAT.Task_Lock.Unlock; -- no effect
84 -- GNAT.Task_Lock.Unlock; -- releases lock
86 -- However, as previously noted, the Task_Lock facility should only
87 -- be used for very local locks where the probability of conflict is
88 -- low, so usually this kind of nesting is not a good idea in any case.
89 -- In more complex locking situations, it is more appropriate to define
90 -- an appropriate protected type to provide the required locking.
92 end GNAT.Task_Lock;