Changes in / [8dbedfc:13073be]
- Files:
-
- 2 added
- 7 deleted
- 30 edited
-
doc/bibliography/pl.bib (modified) (4 diffs)
-
doc/papers/concurrency/Paper.tex (modified) (12 diffs)
-
doc/papers/general/Paper.tex (modified) (25 diffs)
-
doc/related_papers/Buhr94.pdf (deleted)
-
src/Parser/parser.yy (modified) (31 diffs)
-
src/ResolvExpr/AlternativeFinder.cc (modified) (16 diffs)
-
src/Tuples/TupleAssignment.cc (modified) (2 diffs)
-
src/libcfa/concurrency/alarm.c (modified) (2 diffs)
-
src/tests/.expect/io.txt (added)
-
src/tests/.expect/io1.txt (deleted)
-
src/tests/.expect/io2.txt (deleted)
-
src/tests/.expect/math1.x64.txt (modified) (1 diff)
-
src/tests/.expect/math1.x86.txt (modified) (1 diff)
-
src/tests/.expect/math2.x64.txt (modified) (2 diffs)
-
src/tests/.expect/math2.x86.txt (modified) (2 diffs)
-
src/tests/.expect/math3.x64.txt (modified) (1 diff)
-
src/tests/.expect/math3.x86.txt (modified) (1 diff)
-
src/tests/.expect/math4.x64.txt (deleted)
-
src/tests/concurrent/coroutineYield.c (modified) (1 diff)
-
src/tests/concurrent/examples/matrixSum.c (modified) (2 diffs)
-
src/tests/concurrent/signal/block.c (modified) (2 diffs)
-
src/tests/concurrent/signal/disjoint.c (modified) (2 diffs)
-
src/tests/concurrent/signal/wait.c (modified) (2 diffs)
-
src/tests/io.c (added)
-
src/tests/io1.c (deleted)
-
src/tests/io2.c (deleted)
-
src/tests/math1.c (modified) (2 diffs)
-
src/tests/math2.c (modified) (3 diffs)
-
src/tests/math3.c (modified) (2 diffs)
-
src/tests/math4.c (deleted)
-
src/tests/preempt_longrun/Makefile.am (modified) (1 diff)
-
src/tests/preempt_longrun/Makefile.in (modified) (1 diff)
-
src/tests/preempt_longrun/create.c (modified) (2 diffs)
-
src/tests/preempt_longrun/enter.c (modified) (2 diffs)
-
src/tests/preempt_longrun/enter3.c (modified) (2 diffs)
-
src/tests/preempt_longrun/processor.c (modified) (2 diffs)
-
src/tests/preempt_longrun/stack.c (modified) (1 diff)
-
src/tests/preempt_longrun/yield.c (modified) (2 diffs)
-
src/tests/test.py (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
doc/bibliography/pl.bib
r8dbedfc r13073be 377 377 } 378 378 379 @article{Hoare61,380 keywords = {quick sort},381 contributer = {pabuhr@plg},382 author = {C. A. R. Hoare},383 title = {Algorithms 63/64: Partition/Quicksort},384 journal = cacm,385 volume = 4,386 number = 7,387 month = jul,388 year = 1961,389 pages = {321},390 }391 392 379 @article{Cormack81, 393 380 keywords = {}, … … 648 635 year = 2008, 649 636 pages = {8-15}, 650 }651 652 @article{Joung00,653 author = {Joung, Yuh-Jzer},654 title = {Asynchronous group mutual exclusion},655 journal = {Distributed Computing},656 year = {2000},657 month = {Nov},658 volume = {13},659 number = {4},660 pages = {189--206},661 637 } 662 638 … … 5815 5791 @manual{Python, 5816 5792 keywords = {Python}, 5817 contributer = {pabuhr @plg},5793 contributer = {pabuhr}, 5818 5794 title = {Python Reference Manual, Release 2.5}, 5819 5795 author = {Guido van Rossum}, … … 5846 5822 } 5847 5823 5848 @article{Nakaike15, 5849 keywords = {hardware transactional memory}, 5850 contributer = {pabuhr@plg}, 5851 author = {Nakaike, Takuya and Odaira, Rei and Gaudet, Matthew and Michael, Maged M. and Tomari, Hisanobu}, 5852 title = {Quantitative Comparison of Hardware Transactional Memory for Blue Gene/Q, zEnterprise {EC12}, {I}ntel Core, and {POWER8}}, 5853 journal = {SIGARCH Comput. Archit. News}, 5854 volume = {43}, 5855 number = {3}, 5856 month = jun, 5857 year = {2015}, 5858 pages = {144--157}, 5859 publisher = {ACM}, 5860 address = {New York, NY, USA}, 5824 @article{Hoare61, 5825 keywords = {quick sort}, 5826 contributer = {pabuhr@plg}, 5827 author = {C. A. R. Hoare}, 5828 title = {Algorithms 63/64: Partition/Quicksort}, 5829 journal = cacm, 5830 volume = 4, 5831 number = 7, 5832 month = jul, 5833 year = 1961, 5834 pages = {321}, 5861 5835 } 5862 5836 -
doc/papers/concurrency/Paper.tex
r8dbedfc r13073be 70 70 %\DeclareTextCommandDefault{\textunderscore}{\leavevmode\makebox[1.2ex][c]{\rule{1ex}{0.1ex}}} 71 71 \renewcommand{\textunderscore}{\leavevmode\makebox[1.2ex][c]{\rule{1ex}{0.075ex}}} 72 %\def\myCHarFont{\fontencoding{T1}\selectfont}% 73 % \def\{{\ttfamily\upshape\myCHarFont \char`\}}}% 72 74 73 75 \renewcommand*{\thefootnote}{\Alph{footnote}} % hack because fnsymbol does not work … … 739 741 The coroutine main's stack holds the state for the next generation, @f1@ and @f2@, and the code has the three suspend points, representing the three states in the Fibonacci formula, to context switch back to the caller's resume. 740 742 The interface function, @next@, takes a Fibonacci instance and context switches to it using @resume@; 741 on re start, the Fibonacci field, @fn@, contains the next value in the sequence, which is returned.743 on return, the Fibonacci field, @fn@, contains the next value in the sequence, which is returned. 742 744 The first @resume@ is special because it cocalls the coroutine at its coroutine main and allocates the stack; 743 745 when the coroutine main returns, its stack is deallocated. 744 746 Hence, @Fib@ is an object at creation, transitions to a coroutine on its first resume, and transitions back to an object when the coroutine main finishes. 745 747 Figure~\ref{f:Coroutine1State} shows the coroutine version of the C version in Figure~\ref{f:ExternalState}. 746 Coroutine generators are called \newterm{output coroutines} because values are only returned.747 748 Figure~\ref{f:CFAFmt} shows an \newterm{input coroutine}, @Format@, for restructuring text into groups of character s of fixed-size blocks.748 Coroutine generators are called \newterm{output coroutines} because values are returned by the coroutine. 749 750 Figure~\ref{f:CFAFmt} shows an \newterm{input coroutine}, @Format@, for restructuring text into groups of character blocks of fixed size. 749 751 For example, the input of the left is reformatted into the output on the right. 750 752 \begin{quote} … … 761 763 \end{tabular} 762 764 \end{quote} 763 The example takes advantage of resuming a coroutine in the constructor to prime the loops so the first character sent for formatting appears inside the nested loops.765 The example takes advantage of resuming coroutines in the constructor to prime the coroutine loops so the first character sent for formatting appears inside the nested loops. 764 766 The destruction provides a newline if formatted text ends with a full line. 765 767 Figure~\ref{f:CFmt} shows the C equivalent formatter, where the loops of the coroutine are flatten (linearized) and rechecked on each call because execution location is not retained between calls. … … 776 778 void main( Format & fmt ) with( fmt ) { 777 779 for ( ;; ) { 778 for ( g = 0; g < 5; g += 1 ) { // group780 for ( g = 0; g < 5; g += 1 ) { // group 779 781 for ( b = 0; b < 4; b += 1 ) { // block 780 782 `suspend();` … … 812 814 }; 813 815 void format( struct Format * fmt ) { 814 if ( fmt->ch != -1 ) { // not EOF ?816 if ( fmt->ch != -1 ) { // not EOF 815 817 printf( "%c", fmt->ch ); 816 818 fmt->b += 1; … … 821 823 } 822 824 if ( fmt->g == 5 ) { // group 823 printf( "\n" ); // separator825 printf( "\n" ); // separator 824 826 fmt->g = 0; 825 827 } … … 848 850 849 851 The previous examples are \newterm{asymmetric (semi) coroutine}s because one coroutine always calls a resuming function for another coroutine, and the resumed coroutine always suspends back to its last resumer, similar to call/return for normal functions. 850 However, there is no stack growth because @resume@/@suspend@ context switch to existing stack-frames rather than create new ones.851 \newterm{Symmetric (full) coroutine}s have a coroutine call a resuming function for another coroutine, which eventually forms a resuming-callcycle.852 However, there is no stack growth because @resume@/@suspend@ context switch to an existing stack frames rather than create a new one. 853 \newterm{Symmetric (full) coroutine}s have a coroutine call a resuming function for another coroutine, which eventually forms a cycle. 852 854 (The trivial cycle is a coroutine resuming itself.) 853 855 This control flow is similar to recursion for normal routines, but again there is no stack growth from the context switch. … … 933 935 The @start@ function communicates both the number of elements to be produced and the consumer into the producer's coroutine structure. 934 936 Then the @resume@ to @prod@ creates @prod@'s stack with a frame for @prod@'s coroutine main at the top, and context switches to it. 935 @prod@'s coroutine main starts, creates local variables that are retained between coroutine activations, and executes $N$ iterations, each generating two random val ues, calling the consumer to deliver the values, and printing the status returned from the consumer.937 @prod@'s coroutine main starts, creates local variables that are retained between coroutine activations, and executes $N$ iterations, each generating two random vales, calling the consumer to deliver the values, and printing the status returned from the consumer. 936 938 937 939 The producer call to @delivery@ transfers values into the consumer's communication variables, resumes the consumer, and returns the consumer status. 938 940 For the first resume, @cons@'s stack is initialized, creating local variables retained between subsequent activations of the coroutine. 939 The consumer iterates until the @done@ flag is set, prints, increments status, and calls back to the producer via @payment@, and on return from @payment@, prints the receipt from the producer and increments @money@ (inflation).940 The call from the consumer to the @payment@introduces the cycle between producer and consumer.941 The consumer iterates until the @done@ flag is set, prints, increments status, and calls back to the producer's @payment@ member, and on return prints the receipt from the producer and increments the money for the next payment. 942 The call from the consumer to the producer's @payment@ member introduces the cycle between producer and consumer. 941 943 When @payment@ is called, the consumer copies values into the producer's communication variable and a resume is executed. 942 The context switch restarts the producer at the point where it was last context switched , so it continues in@delivery@ after the resume.943 944 @delivery@ returns the status value in @prod@'s coroutine main, where the status is printed.944 The context switch restarts the producer at the point where it was last context switched and it continues in member @delivery@ after the resume. 945 946 The @delivery@ member returns the status value in @prod@'s @main@ member, where the status is printed. 945 947 The loop then repeats calling @delivery@, where each call resumes the consumer coroutine. 946 948 The context switch to the consumer continues in @payment@. 947 The consumer increments and returns the receipt to the call in @cons@'s coroutine main.949 The consumer increments and returns the receipt to the call in @cons@'s @main@ member. 948 950 The loop then repeats calling @payment@, where each call resumes the producer coroutine. 949 951 … … 952 954 The context switch restarts @cons@ in @payment@ and it returns with the last receipt. 953 955 The consumer terminates its loops because @done@ is true, its @main@ terminates, so @cons@ transitions from a coroutine back to an object, and @prod@ reactivates after the resume in @stop@. 954 @stop@ returns and @prod@'s coroutine mainterminates.956 The @stop@ member returns and @prod@'s @main@ member terminates. 955 957 The program main restarts after the resume in @start@. 956 @start@ returns and the program main terminates. 957 958 959 \subsection{Coroutine Implementation} 960 961 A significant implementation challenge for coroutines (and threads, see section \ref{threads}) is adding extra fields and executing code after/before the coroutine constructor/destructor and coroutine main to create/initialize/de-initialize/destroy extra fields and the stack. 962 There are several solutions to this problem and the chosen option forced the \CFA coroutine design. 963 964 Object-oriented inheritance provides extra fields and code in a restricted context, but it requires programmers to explicitly perform the inheritance: 965 \begin{cfa} 966 struct mycoroutine $\textbf{\textsf{inherits}}$ baseCoroutine { ... } 967 \end{cfa} 968 and the programming language (and possibly its tool set, \eg debugger) may need to understand @baseCoroutine@ because of the stack. 969 Furthermore, the execution of constructs/destructors is in the wrong order for certain operations, \eg for threads; 970 \eg, if the thread is implicitly started, it must start \emph{after} all constructors, because the thread relies on a completely initialized object, but the inherited constructor runs \emph{before} the derived. 971 972 An alternatively is composition: 973 \begin{cfa} 974 struct mycoroutine { 975 ... // declarations 976 baseCoroutine dummy; // composition, last declaration 977 } 978 \end{cfa} 979 which also requires an explicit declaration that must be the last one to ensure correct initialization order. 980 However, there is nothing preventing wrong placement or multiple declarations. 958 The @start@ member returns and the program main terminates. 959 960 961 \subsubsection{Construction} 962 963 One important design challenge for implementing coroutines and threads (shown in section \ref{threads}) is that the runtime system needs to run code after the user-constructor runs to connect the fully constructed object into the system. 964 In the case of coroutines, this challenge is simpler since there is no non-determinism from preemption or scheduling. 965 However, the underlying challenge remains the same for coroutines and threads. 966 967 The runtime system needs to create the coroutine's stack and, more importantly, prepare it for the first resumption. 968 The timing of the creation is non-trivial since users expect both to have fully constructed objects once execution enters the coroutine main and to be able to resume the coroutine from the constructor. 969 There are several solutions to this problem but the chosen option effectively forces the design of the coroutine. 970 971 Furthermore, \CFA faces an extra challenge as polymorphic routines create invisible thunks when cast to non-polymorphic routines and these thunks have function scope. 972 For example, the following code, while looking benign, can run into undefined behaviour because of thunks: 973 974 \begin{cfa} 975 // async: Runs function asynchronously on another thread 976 forall(otype T) 977 extern void async(void (*func)(T*), T* obj); 978 979 forall(otype T) 980 void noop(T*) {} 981 982 void bar() { 983 int a; 984 async(noop, &a); // start thread running noop with argument a 985 } 986 \end{cfa} 987 988 The generated C code\footnote{Code trimmed down for brevity} creates a local thunk to hold type information: 989 990 \begin{cfa} 991 extern void async(/* omitted */, void (*func)(void*), void* obj); 992 993 void noop(/* omitted */, void* obj){} 994 995 void bar(){ 996 int a; 997 void _thunk0(int* _p0){ 998 /* omitted */ 999 noop(/* omitted */, _p0); 1000 } 1001 /* omitted */ 1002 async(/* omitted */, ((void (*)(void*))(&_thunk0)), (&a)); 1003 } 1004 \end{cfa} 1005 The problem in this example is a storage management issue, the function pointer @_thunk0@ is only valid until the end of the block, which limits the viable solutions because storing the function pointer for too long causes undefined behaviour; \ie the stack-based thunk being destroyed before it can be used. 1006 This challenge is an extension of challenges that come with second-class routines. 1007 Indeed, GCC nested routines also have the limitation that nested routine cannot be passed outside of the declaration scope. 1008 The case of coroutines and threads is simply an extension of this problem to multiple call stacks. 1009 1010 1011 \subsubsection{Alternative: Composition} 1012 1013 One solution to this challenge is to use composition/containment, where coroutine fields are added to manage the coroutine. 1014 1015 \begin{cfa} 1016 struct Fibonacci { 1017 int fn; // used for communication 1018 coroutine c; // composition 1019 }; 1020 1021 void FibMain(void*) { 1022 //... 1023 } 1024 1025 void ?{}(Fibonacci& this) { 1026 this.fn = 0; 1027 // Call constructor to initialize coroutine 1028 (this.c){myMain}; 1029 } 1030 \end{cfa} 1031 The downside of this approach is that users need to correctly construct the coroutine handle before using it. 1032 Like any other objects, the user must carefully choose construction order to prevent usage of objects not yet constructed. 1033 However, in the case of coroutines, users must also pass to the coroutine information about the coroutine main, like in the previous example. 1034 This opens the door for user errors and requires extra runtime storage to pass at runtime information that can be known statically. 1035 1036 1037 \subsubsection{Alternative: Reserved keyword} 1038 1039 The next alternative is to use language support to annotate coroutines as follows: 1040 \begin{cfa} 1041 coroutine Fibonacci { 1042 int fn; // used for communication 1043 }; 1044 \end{cfa} 1045 The @coroutine@ keyword means the compiler can find and inject code where needed. 1046 The downside of this approach is that it makes coroutine a special case in the language. 1047 Users wanting to extend coroutines or build their own for various reasons can only do so in ways offered by the language. 1048 Furthermore, implementing coroutines without language supports also displays the power of the programming language used. 1049 While this is ultimately the option used for idiomatic \CFA code, coroutines and threads can still be constructed by users without using the language support. 1050 The reserved keywords are only present to improve ease of use for the common cases. 1051 1052 1053 \subsubsection{Alternative: Lambda Objects} 981 1054 982 1055 For coroutines as for threads, many implementations are based on routine pointers or function objects~\cite{Butenhof97, C++14, MS:VisualC++, BoostCoroutines15}. 983 For example, Boost implements coroutines in terms of four functor object -types:1056 For example, Boost implements coroutines in terms of four functor object types: 984 1057 \begin{cfa} 985 1058 asymmetric_coroutine<>::pull_type … … 988 1061 symmetric_coroutine<>::yield_type 989 1062 \end{cfa} 990 Similarly, the canonical threading paradigm is often based on function pointers, \eg @pthread@~\cite{pthreads}, \Csharp~\cite{Csharp}, Go~\cite{Go}, and Scala~\cite{Scala}. 991 However, the generic thread-handle (identifier) is limited (few operations), unless it is wrapped in a custom type. 992 \begin{cfa} 993 void mycor( coroutine_t cid, void * arg ) { 994 int * value = (int *)arg; $\C{// type unsafe, pointer-size only}$ 1063 Often, the canonical threading paradigm in languages is based on function pointers, @pthread@ being one of the most well-known examples. 1064 The main problem of this approach is that the thread usage is limited to a generic handle that must otherwise be wrapped in a custom type. 1065 Since the custom type is simple to write in \CFA and solves several issues, added support for routine/lambda based coroutines adds very little. 1066 1067 A variation of this would be to use a simple function pointer in the same way @pthread@ does for threads: 1068 \begin{cfa} 1069 void foo( coroutine_t cid, void* arg ) { 1070 int* value = (int*)arg; 995 1071 // Coroutine body 996 1072 } 1073 997 1074 int main() { 998 int input = 0, output; 999 coroutine_t cid = coroutine_create( &mycor, (void *)&input ); $\C{// type unsafe, pointer-size only}$ 1000 coroutine_resume( cid, (void *)input, (void **)&output ); $\C{// type unsafe, pointer-size only}$ 1001 } 1002 \end{cfa} 1003 Since the custom type is simple to write in \CFA and solves several issues, added support for routine/lambda-based coroutines adds very little. 1004 1005 The selected approach is to use language support by introducing a new kind of aggregate (structure): 1006 \begin{cfa} 1007 coroutine Fibonacci { 1008 int fn; // communication variables 1075 int value = 0; 1076 coroutine_t cid = coroutine_create( &foo, (void*)&value ); 1077 coroutine_resume( &cid ); 1078 } 1079 \end{cfa} 1080 This semantics is more common for thread interfaces but coroutines work equally well. 1081 As discussed in section \ref{threads}, this approach is superseded by static approaches in terms of expressivity. 1082 1083 1084 \subsubsection{Alternative: Trait-Based Coroutines} 1085 1086 Finally, the underlying approach, which is the one closest to \CFA idioms, is to use trait-based lazy coroutines. 1087 This approach defines a coroutine as anything that satisfies the trait @is_coroutine@ (as defined below) and is used as a coroutine. 1088 1089 \begin{cfa} 1090 trait is_coroutine(dtype T) { 1091 void main(T& this); 1092 coroutine_desc* get_coroutine(T& this); 1009 1093 }; 1010 \end{cfa} 1011 The @coroutine@ keyword means the compiler (and tool set) can find and inject code where needed. 1012 The downside of this approach is that it makes coroutine a special case in the language. 1013 Users wanting to extend coroutines or build their own for various reasons can only do so in ways offered by the language. 1014 Furthermore, implementing coroutines without language supports also displays the power of a programming language. 1015 While this is ultimately the option used for idiomatic \CFA code, coroutines and threads can still be constructed without using the language support. 1016 The reserved keyword eases use for the common cases. 1017 1018 Part of the mechanism to generalize coroutines is using a \CFA trait, which defines a coroutine as anything satisfying the trait @is_coroutine@, and this trait is used to restrict coroutine-manipulation functions: 1019 \begin{cfa} 1020 trait is_coroutine( dtype T ) { 1021 void main( T & this ); 1022 coroutine_desc * get_coroutine( T & this ); 1094 1095 forall( dtype T | is_coroutine(T) ) void suspend(T&); 1096 forall( dtype T | is_coroutine(T) ) void resume (T&); 1097 \end{cfa} 1098 This ensures that an object is not a coroutine until @resume@ is called on the object. 1099 Correspondingly, any object that is passed to @resume@ is a coroutine since it must satisfy the @is_coroutine@ trait to compile. 1100 The advantage of this approach is that users can easily create different types of coroutines, for example, changing the memory layout of a coroutine is trivial when implementing the @get_coroutine@ routine. 1101 The \CFA keyword @coroutine@ simply has the effect of implementing the getter and forward declarations required for users to implement the main routine. 1102 1103 \begin{center} 1104 \begin{tabular}{c c c} 1105 \begin{cfa}[tabsize=3] 1106 coroutine MyCoroutine { 1107 int someValue; 1023 1108 }; 1024 forall( dtype T | is_coroutine(T) ) void get_coroutine( T & ); 1025 forall( dtype T | is_coroutine(T) ) void suspend( T & ); 1026 forall( dtype T | is_coroutine(T) ) void resume( T & ); 1027 \end{cfa} 1028 This definition ensures there is a statically-typed @main@ function that is the starting point (first stack frame) of a coroutine. 1029 No return value or additional parameters are necessary for this function, because the coroutine type allows an arbitrary number of interface functions with corresponding arbitrary typed input/output values. 1030 As well, any object passed to @suspend@ and @resume@ is a coroutine since it must satisfy the @is_coroutine@ trait to compile. 1031 The advantage of this approach is that users can easily create different types of coroutines, for example, changing the memory layout of a coroutine is trivial when implementing the @get_coroutine@ routine. 1032 The \CFA keyword @coroutine@ implicitly implements the getter and forward declarations required for implementing the coroutine main: 1033 \begin{cquote} 1034 \begin{tabular}{@{}ccc@{}} 1035 \begin{cfa} 1036 coroutine MyCor { 1037 int value; 1038 1109 \end{cfa} & == & \begin{cfa}[tabsize=3] 1110 struct MyCoroutine { 1111 int someValue; 1112 coroutine_desc __cor; 1039 1113 }; 1040 \end{cfa} 1041 & {\Large $\Rightarrow$} & 1042 \begin{tabular}{@{}ccc@{}} 1043 \begin{cfa} 1044 struct MyCor { 1045 int value; 1046 coroutine_desc cor; 1114 1115 static inline 1116 coroutine_desc* get_coroutine( 1117 struct MyCoroutine& this 1118 ) { 1119 return &this.__cor; 1120 } 1121 1122 void main(struct MyCoroutine* this); 1123 \end{cfa} 1124 \end{tabular} 1125 \end{center} 1126 1127 The combination of these two approaches allows users new to coroutining and concurrency to have an easy and concise specification, while more advanced users have tighter control on memory layout and initialization. 1128 1129 \subsection{Thread Interface}\label{threads} 1130 The basic building blocks of multithreading in \CFA are \textbf{cfathread}. 1131 Both user and kernel threads are supported, where user threads are the concurrency mechanism and kernel threads are the parallel mechanism. 1132 User threads offer a flexible and lightweight interface. 1133 A thread can be declared using a struct declaration @thread@ as follows: 1134 1135 \begin{cfa} 1136 thread foo {}; 1137 \end{cfa} 1138 1139 As for coroutines, the keyword is a thin wrapper around a \CFA trait: 1140 1141 \begin{cfa} 1142 trait is_thread(dtype T) { 1143 void ^?{}(T & mutex this); 1144 void main(T & this); 1145 thread_desc* get_thread(T & this); 1047 1146 }; 1048 1147 \end{cfa} 1049 & 1050 \begin{cfa} 1051 static inline coroutine_desc * 1052 get_coroutine( MyCor & this ) { 1053 return &this.cor; 1054 } 1055 \end{cfa} 1056 & 1057 \begin{cfa} 1058 void main( MyCor * this ); 1059 1060 1061 1062 \end{cfa} 1063 \end{tabular} 1064 \end{tabular} 1065 \end{cquote} 1066 The combination of these two approaches allows an easy and concise specification to coroutining (and concurrency) for normal users, while more advanced users have tighter control on memory layout and initialization. 1067 1068 1069 \subsection{Thread Interface} 1070 \label{threads} 1071 1072 Both user and kernel threads are supported, where user threads provide concurrency and kernel threads provide parallelism. 1073 Like coroutines and for the same design reasons, the selected approach for user threads is to use language support by introducing a new kind of aggregate (structure) and a \CFA trait: 1074 \begin{cquote} 1075 \begin{tabular}{@{}c@{\hspace{2\parindentlnth}}c@{}} 1076 \begin{cfa} 1077 thread myThread { 1078 // communication variables 1079 }; 1080 1081 1082 \end{cfa} 1083 & 1084 \begin{cfa} 1085 trait is_thread( dtype T ) { 1086 void main( T & this ); 1087 thread_desc * get_thread( T & this ); 1088 void ^?{}( T & `mutex` this ); 1089 }; 1090 \end{cfa} 1091 \end{tabular} 1092 \end{cquote} 1093 (The qualifier @mutex@ for the destructor parameter is discussed in Section~\ref{s:Monitors}.) 1094 Like a coroutine, the statically-typed @main@ function is the starting point (first stack frame) of a user thread. 1095 The difference is that a coroutine borrows a thread from its caller, so the first thread resuming a coroutine creates an instance of @main@; 1096 whereas, a user thread receives its own thread from the runtime system, which starts in @main@ as some point after the thread constructor is run.\footnote{ 1097 The \lstinline@main@ function is already a special routine in C (where the program begins), so it is a natural extension of the semantics to use overloading to declare mains for different coroutines/threads (the normal main being the main of the initial thread).} 1098 No return value or additional parameters are necessary for this function, because the task type allows an arbitrary number of interface functions with corresponding arbitrary typed input/output values. 1099 1100 \begin{comment} % put in appendix with coroutine version ??? 1148 1149 Obviously, for this thread implementation to be useful it must run some user code. 1150 Several other threading interfaces use a function-pointer representation as the interface of threads (for example \Csharp~\cite{Csharp} and Scala~\cite{Scala}). 1151 However, this proposal considers that statically tying a @main@ routine to a thread supersedes this approach. 1152 Since the @main@ routine is already a special routine in \CFA (where the program begins), it is a natural extension of the semantics to use overloading to declare mains for different threads (the normal main being the main of the initial thread). 1101 1153 As such the @main@ routine of a thread can be defined as 1102 1154 \begin{cfa} … … 1137 1189 } 1138 1190 \end{cfa} 1191 1139 1192 A consequence of the strongly typed approach to main is that memory layout of parameters and return values to/from a thread are now explicitly specified in the \textbf{api}. 1140 \end{comment} 1141 1142 For user threads to be useful, it must be possible to start and stop the underlying thread, and wait for it to complete execution.1143 While using an API such as @fork@ and @join@ is relatively common, such an interface is awkward and unnecessary.1144 A simple approach is to use allocation/deallocation principles, and have threads implicitly @fork@ after construction and @join@ before destruction. 1145 \begin{cfa} 1146 thread World {}; 1147 void main( World & this) {1193 1194 Of course, for threads to be useful, it must be possible to start and stop threads and wait for them to complete execution. 1195 While using an \textbf{api} such as @fork@ and @join@ is relatively common in the literature, such an interface is unnecessary. 1196 Indeed, the simplest approach is to use \textbf{raii} principles and have threads @fork@ after the constructor has completed and @join@ before the destructor runs. 1197 \begin{cfa} 1198 thread World; 1199 1200 void main(World & this) { 1148 1201 sout | "World!" | endl; 1149 1202 } 1150 int main() { 1151 World w`[10]`; $\C{// implicit forks after creation}$ 1152 sout | "Hello " | endl; $\C{// "Hello " and 10 "World!" printed concurrently}$ 1153 } $\C{// implicit joins before destruction}$ 1154 \end{cfa} 1155 This semantics ensures a thread is started and stopped exactly once, eliminating some programming error, and scales to multiple threads for basic (termination) synchronization. 1156 This tree-structure (lattice) create/delete from C block-structure is generalized by using dynamic allocation, so threads can outlive the scope in which they are created, much like dynamically allocating memory lets objects outlive the scope in which they are created. 1157 \begin{cfa} 1158 int main() { 1159 MyThread * heapLived; 1203 1204 void main() { 1205 World w; 1206 // Thread forks here 1207 1208 // Printing "Hello " and "World!" are run concurrently 1209 sout | "Hello " | endl; 1210 1211 // Implicit join at end of scope 1212 } 1213 \end{cfa} 1214 1215 This semantic has several advantages over explicit semantics: a thread is always started and stopped exactly once, users cannot make any programming errors, and it naturally scales to multiple threads meaning basic synchronization is very simple. 1216 1217 \begin{cfa} 1218 thread MyThread { 1219 //... 1220 }; 1221 1222 // main 1223 void main(MyThread& this) { 1224 //... 1225 } 1226 1227 void foo() { 1228 MyThread thrds[10]; 1229 // Start 10 threads at the beginning of the scope 1230 1231 DoStuff(); 1232 1233 // Wait for the 10 threads to finish 1234 } 1235 \end{cfa} 1236 1237 However, one of the drawbacks of this approach is that threads always form a tree where nodes must always outlive their children, \ie they are always destroyed in the opposite order of construction because of C scoping rules. 1238 This restriction is relaxed by using dynamic allocation, so threads can outlive the scope in which they are created, much like dynamically allocating memory lets objects outlive the scope in which they are created. 1239 1240 \begin{cfa} 1241 thread MyThread { 1242 //... 1243 }; 1244 1245 void main(MyThread& this) { 1246 //... 1247 } 1248 1249 void foo() { 1250 MyThread* long_lived; 1160 1251 { 1161 MyThread blockLived; $\C{// fork block-based thread}$ 1162 heapLived = `new`( MyThread ); $\C{// fork heap-based thread}$ 1163 ... 1164 } $\C{// join block-based thread}$ 1165 ... 1166 `delete`( heapLived ); $\C{// join heap-based thread}$ 1167 } 1168 \end{cfa} 1169 The heap-based approach allows arbitrary thread-creation topologies, with respect to fork/join-style concurrency. 1170 1171 Figure~\ref{s:ConcurrentMatrixSummation} shows concurrently adding the rows of a matrix and then totalling the subtotals sequential, after all the row threads have terminated. 1172 The program uses heap-based threads because each thread needs different constructor values. 1173 (Python provides a simple iteration mechanism to initialize array elements to different values allowing stack allocation.) 1174 The allocation/deallocation pattern appears unusual because allocated objects are immediately deleted without any intervening code. 1175 However, for threads, the deletion provides implicit synchronization, which is the intervening code. 1176 While the subtotals are added in linear order rather than completion order, which slight inhibits concurrency, the computation is restricted by the critical-path thread (\ie the thread that takes the longest), and so any inhibited concurrency is very small as totalling the subtotals is trivial. 1177 1178 \begin{figure} 1179 \begin{cfa} 1180 thread Adder { 1181 int * row, cols, & subtotal; $\C{// communication}$ 1182 }; 1183 void ?{}( Adder & adder, int row[], int cols, int & subtotal ) { 1184 adder.[ row, cols, &subtotal ] = [ row, cols, &subtotal ]; 1185 } 1186 void main( Adder & adder ) with( adder ) { 1187 subtotal = 0; 1188 for ( int c = 0; c < cols; c += 1 ) { 1189 subtotal += row[c]; 1190 } 1191 } 1192 int main() { 1193 const int rows = 10, cols = 1000; 1194 int matrix[rows][cols], subtotals[rows], total = 0; 1195 // read matrix 1196 Adder * adders[rows]; 1197 for ( int r = 0; r < rows; r += 1 ) { $\C{// start threads to sum rows}$ 1198 adders[r] = new( matrix[r], cols, &subtotals[r] ); 1199 } 1200 for ( int r = 0; r < rows; r += 1 ) { $\C{// wait for threads to finish}$ 1201 delete( adders[r] ); $\C{// termination join}$ 1202 total += subtotals[r]; $\C{// total subtotal}$ 1203 } 1204 sout | total | endl; 1205 } 1206 \end{cfa} 1207 \caption{Concurrent Matrix Summation} 1208 \label{s:ConcurrentMatrixSummation} 1209 \end{figure} 1210 1211 1212 \section{Synchronization / Mutual Exclusion} 1213 1214 Uncontrolled non-deterministic execution is meaningless. 1215 To reestablish meaningful execution requires mechanisms to reintroduce determinism (control non-determinism), called synchronization and mutual exclusion, where synchronization is a timing relationship among threads and mutual exclusion is an access-control mechanism on data shared by threads. 1216 Since many deterministic challenges appear with the use of mutable shared state, some languages/libraries disallow it (Erlang~\cite{Erlang}, Haskell~\cite{Haskell}, Akka~\cite{Akka} (Scala)). 1217 In these paradigms, interaction among concurrent objects is performed by stateless message-passing~\cite{Thoth,Harmony,V-Kernel} or other paradigms closely relate to networking concepts (\eg channels~\cite{CSP,Go}). 1218 However, in call/return-based languages, these approaches force a clear distinction (\ie introduce a new programming paradigm) between non-concurrent and concurrent computation (\ie function call versus message passing). 1219 This distinction means a programmers needs to learn two sets of design patterns. 1252 // Start a thread at the beginning of the scope 1253 MyThread short_lived; 1254 1255 // create another thread that will outlive the thread in this scope 1256 long_lived = new MyThread; 1257 1258 DoStuff(); 1259 1260 // Wait for the thread short_lived to finish 1261 } 1262 DoMoreStuff(); 1263 1264 // Now wait for the long_lived to finish 1265 delete long_lived; 1266 } 1267 \end{cfa} 1268 1269 1270 % ====================================================================== 1271 % ====================================================================== 1272 \section{Concurrency} 1273 % ====================================================================== 1274 % ====================================================================== 1275 Several tools can be used to solve concurrency challenges. 1276 Since many of these challenges appear with the use of mutable shared state, some languages and libraries simply disallow mutable shared state (Erlang~\cite{Erlang}, Haskell~\cite{Haskell}, Akka (Scala)~\cite{Akka}). 1277 In these paradigms, interaction among concurrent objects relies on message passing~\cite{Thoth,Harmony,V-Kernel} or other paradigms closely relate to networking concepts (channels~\cite{CSP,Go} for example). 1278 However, in languages that use routine calls as their core abstraction mechanism, these approaches force a clear distinction between concurrent and non-concurrent paradigms (\ie message passing versus routine calls). 1279 This distinction in turn means that, in order to be effective, programmers need to learn two sets of design patterns. 1220 1280 While this distinction can be hidden away in library code, effective use of the library still has to take both paradigms into account. 1221 In contrast, approaches based on statefull models more closely resemble the standard call/return programming-model, resulting in a single programming paradigm. 1222 1223 At the lowest level, concurrent control is implemented as atomic operations, upon which different kinds of locks mechanism are constructed, \eg semaphores~\cite{Dijkstra68b} and path expressions~\cite{Campbell74}. 1224 However, for productivity it is always desirable to use the highest-level construct that provides the necessary efficiency~\cite{Hochstein05}. 1225 A newer approach is transactional memory~\cite{Herlihy93}. 1226 While this approach is pursued in hardware~\cite{Nakaike15} and system languages, like \CC~\cite{Cpp-Transactions}, the performance and feature set is still too restrictive to be the main concurrency paradigm for system languages, which is why it was rejected as the core paradigm for concurrency in \CFA. 1227 1228 One of the most natural, elegant, and efficient mechanisms for synchronization and mutual exclusion for shared-memory systems is the \emph{monitor}. 1281 1282 Approaches based on shared memory are more closely related to non-concurrent paradigms since they often rely on basic constructs like routine calls and shared objects. 1283 At the lowest level, concurrent paradigms are implemented as atomic operations and locks. 1284 Many such mechanisms have been proposed, including semaphores~\cite{Dijkstra68b} and path expressions~\cite{Campbell74}. 1285 However, for productivity reasons it is desirable to have a higher-level construct be the core concurrency paradigm~\cite{Hochstein05}. 1286 1287 An approach that is worth mentioning because it is gaining in popularity is transactional memory~\cite{Herlihy93}. 1288 While this approach is even pursued by system languages like \CC~\cite{Cpp-Transactions}, the performance and feature set is currently too restrictive to be the main concurrency paradigm for system languages, which is why it was rejected as the core paradigm for concurrency in \CFA. 1289 1290 One of the most natural, elegant, and efficient mechanisms for synchronization and communication, especially for shared-memory systems, is the \emph{monitor}. 1229 1291 Monitors were first proposed by Brinch Hansen~\cite{Hansen73} and later described and extended by C.A.R.~Hoare~\cite{Hoare74}. 1230 Many programming languages -- \eg Concurrent Pascal~\cite{ConcurrentPascal}, Mesa~\cite{Mesa}, Modula~\cite{Modula-2}, Turing~\cite{Turing:old}, Modula-3~\cite{Modula-3}, NeWS~\cite{NeWS}, Emerald~\cite{Emerald}, \uC~\cite{Buhr92a} and Java~\cite{Java} --provide monitors as explicit language constructs.1292 Many programming languages---\eg Concurrent Pascal~\cite{ConcurrentPascal}, Mesa~\cite{Mesa}, Modula~\cite{Modula-2}, Turing~\cite{Turing:old}, Modula-3~\cite{Modula-3}, NeWS~\cite{NeWS}, Emerald~\cite{Emerald}, \uC~\cite{Buhr92a} and Java~\cite{Java}---provide monitors as explicit language constructs. 1231 1293 In addition, operating-system kernels and device drivers have a monitor-like structure, although they often use lower-level primitives such as semaphores or locks to simulate monitors. 1232 For these reasons, this project proposes monitors as the core concurrency construct, upon which even higher-level approaches can be easily constructed.. 1233 1234 1235 \subsection{Mutual Exclusion} 1236 1237 A group of instructions manipulating a specific instance of shared data that must be performed atomically is called an (individual) \newterm{critical-section}~\cite{Dijkstra65}. 1238 A generalization is a \newterm{group critical-section}~\cite{Joung00}, where multiple tasks with the same session may use the resource simultaneously, but different sessions may not use the resource simultaneously. 1239 The readers/writer problem~\cite{Courtois71} is an instance of a group critical-section, where readers have the same session and all writers have a unique session. 1240 \newterm{Mutual exclusion} enforces the correction number of threads are using a critical section at the same time. 1241 1294 For these reasons, this project proposes monitors as the core concurrency construct. 1295 1296 1297 \subsection{Basics} 1298 1299 Non-determinism requires concurrent systems to offer support for mutual-exclusion and synchronization. 1300 Mutual-exclusion is the concept that only a fixed number of threads can access a critical section at any given time, where a critical section is a group of instructions on an associated portion of data that requires the restricted access. 1301 On the other hand, synchronization enforces relative ordering of execution and synchronization tools provide numerous mechanisms to establish timing relationships among threads. 1302 1303 1304 \subsubsection{Mutual-Exclusion} 1305 1306 As mentioned above, mutual-exclusion is the guarantee that only a fix number of threads can enter a critical section at once. 1242 1307 However, many solutions exist for mutual exclusion, which vary in terms of performance, flexibility and ease of use. 1243 Methods range from low-level locks, which are fast and flexible but require significant attention for correctness, to higher-level concurrency techniques, which sacrifice some performanceto improve ease of use.1244 Ease of use comes by either guaranteeing some problems cannot occur (\eg deadlock free), or by offering a more explicit coupling between shared data andcritical section.1308 Methods range from low-level locks, which are fast and flexible but require significant attention to be correct, to higher-level concurrency techniques, which sacrifice some performance in order to improve ease of use. 1309 Ease of use comes by either guaranteeing some problems cannot occur (\eg being deadlock free) or by offering a more explicit coupling between data and corresponding critical section. 1245 1310 For example, the \CC @std::atomic<T>@ offers an easy way to express mutual-exclusion on a restricted set of operations (\eg reading/writing large types atomically). 1246 However, a significant challenge with (low-level) locks is composability because it takes careful organization for multiple locks to be used while preventing deadlock.1247 Easing composability is another feature higher-level mutual-exclusion mechanisms offer.1248 1249 1250 \subsection{Synchronization} 1251 1252 Synchronization enforces relative ordering of execution, and synchronization tools provide numerous mechanisms to establish these timing relationships. 1253 Low-level synchronization primitives offer good performance and flexibility at the cost of ease of use.1254 Higher-level mechanisms often simplify usage by adding better coupling between synchronization and data (\eg message passing), or offering a simpler solution to otherwise involved challenges, \eg barrier lock.1311 Another challenge with low-level locks is composability. 1312 Locks have restricted composability because it takes careful organizing for multiple locks to be used while preventing deadlocks. 1313 Easing composability is another feature higher-level mutual-exclusion mechanisms often offer. 1314 1315 1316 \subsubsection{Synchronization} 1317 1318 As with mutual-exclusion, low-level synchronization primitives often offer good performance and good flexibility at the cost of ease of use. 1319 Again, higher-level mechanisms often simplify usage by adding either better coupling between synchronization and data (\eg message passing) or offering a simpler solution to otherwise involved challenges. 1255 1320 As mentioned above, synchronization can be expressed as guaranteeing that event \textit{X} always happens before \textit{Y}. 1256 Often synchronization is used to order access to a critical section, \eg ensuring the next kind of thread to enter a critical section is a reader thread 1257 If a writer thread is scheduled for next access, but another reader thread acquires the critical section first, the reader has \newterm{barged}. 1258 Barging can result in staleness/freshness problems, where a reader barges ahead of a write and reads temporally stale data, or a writer barges ahead of another writer overwriting data with a fresh value preventing the previous value from having an opportunity to be read. 1321 Most of the time, synchronization happens within a critical section, where threads must acquire mutual-exclusion in a certain order. 1322 However, it may also be desirable to guarantee that event \textit{Z} does not occur between \textit{X} and \textit{Y}. 1323 Not satisfying this property is called \textbf{barging}. 1324 For example, where event \textit{X} tries to effect event \textit{Y} but another thread acquires the critical section and emits \textit{Z} before \textit{Y}. 1325 The classic example is the thread that finishes using a resource and unblocks a thread waiting to use the resource, but the unblocked thread must compete to acquire the resource. 1259 1326 Preventing or detecting barging is an involved challenge with low-level locks, which can be made much easier by higher-level constructs. 1260 This challenge is often split into two different approaches, barging avoidance and barging prevention. 1261 Algorithms that allow a barger but divert it until later are avoiding the barger, while algorithms that preclude a barger from entering during synchronization in the critical section prevent the barger completely. 1262 baton-pass locks~\cite{Andrews89} between threads instead of releasing the locks are said to be using barging prevention. 1263 1264 1327 This challenge is often split into two different methods, barging avoidance and barging prevention. 1328 Algorithms that use flag variables to detect barging threads are said to be using barging avoidance, while algorithms that baton-pass locks~\cite{Andrews89} between threads instead of releasing the locks are said to be using barging prevention. 1329 1330 1331 % ====================================================================== 1332 % ====================================================================== 1265 1333 \section{Monitors} 1266 \label{s:Monitors} 1267 1334 % ====================================================================== 1335 % ====================================================================== 1268 1336 A \textbf{monitor} is a set of routines that ensure mutual-exclusion when accessing shared state. 1269 1337 More precisely, a monitor is a programming technique that associates mutual-exclusion to routine scopes, as opposed to mutex locks, where mutual-exclusion is defined by lock/release calls independently of any scoping of the calling routine. … … 2433 2501 Given these building blocks, it is possible to reproduce all three of the popular paradigms. 2434 2502 Indeed, \textbf{uthread} is the default paradigm in \CFA. 2435 However, disabling \textbf{preemption} on a cluster means threads effectively become fibers.2503 However, disabling \textbf{preemption} on the \textbf{cfacluster} means \textbf{cfathread} effectively become \textbf{fiber}. 2436 2504 Since several \textbf{cfacluster} with different scheduling policy can coexist in the same application, this allows \textbf{fiber} and \textbf{uthread} to coexist in the runtime of an application. 2437 2505 Finally, it is possible to build executors for thread pools from \textbf{uthread} or \textbf{fiber}, which includes specialized jobs like actors~\cite{Actors}. -
doc/papers/general/Paper.tex
r8dbedfc r13073be 243 243 Nevertheless, C, first standardized almost forty years ago~\cite{ANSI89:C}, lacks many features that make programming in more modern languages safer and more productive. 244 244 245 \CFA (pronounced ``C-for-all'', and written \CFA or Cforall) is an evolutionary extension of the C programming language that adds modern language-features to C, while maintaining source and runtime compatibility in the familiar C programming model.245 \CFA (pronounced ``C-for-all'', and written \CFA or Cforall) is an evolutionary extension of the C programming language that adds modern language-features to C, while maintaining both source and runtime compatibility with C and a familiar programming model for programmers. 246 246 The four key design goals for \CFA~\cite{Bilson03} are: 247 247 (1) The behaviour of standard C code must remain the same when translated by a \CFA compiler as when translated by a C compiler; … … 273 273 Starting with a translator versus a compiler makes it easier and faster to generate and debug C object-code rather than intermediate, assembler or machine code. 274 274 The translator design is based on the \emph{visitor pattern}, allowing multiple passes over the abstract code-tree, which works well for incrementally adding new feature through additional visitor passes. 275 At the heart of the translator is the type resolver, which handles the polymorphic function/type overload-resolution.275 At the heart of the translator is the type resolver, which handles the polymorphic routine/type overload-resolution. 276 276 % @plg2[8]% cd cfa-cc/src; cloc libcfa 277 277 % ------------------------------------------------------------------------------- … … 310 310 311 311 Finally, it is impossible to describe a programming language without usages before definitions. 312 Therefore, syntax and semantics appear before explanations , and related work (Section~\ref{s:RelatedWork}) is deferred until \CFA is presented;313 hence, patience is necessary until details are discussed.312 Therefore, syntax and semantics appear before explanations; 313 hence, patience is necessary until details are presented. 314 314 315 315 … … 329 329 \end{quote} 330 330 \vspace{-9pt} 331 C already has a limited form of ad-hoc polymorphism in its basic arithmetic operators, which apply to a variety of different types using identical syntax.331 C already has a limited form of ad-hoc polymorphism in the form of its basic arithmetic operators, which apply to a variety of different types using identical syntax. 332 332 \CFA extends the built-in operator overloading by allowing users to define overloads for any function, not just operators, and even any variable; 333 333 Section~\ref{sec:libraries} includes a number of examples of how this overloading simplifies \CFA programming relative to C. … … 653 653 } 654 654 \end{cfa} 655 Since @pair( T *, T * )@ is a concrete type, there are no implicit parameters passed to @lexcmp@, so the generated code is identical to a function written in standard C using @void *@, yet the \CFA version is type-checked to ensure the members of both pairs and the arguments to the comparison function match in type.655 Since @pair( T *, T * )@ is a concrete type, there are no implicit parameters passed to @lexcmp@, so the generated code is identical to a function written in standard C using @void *@, yet the \CFA version is type-checked to ensure the fields of both pairs and the arguments to the comparison function match in type. 656 656 657 657 Another useful pattern enabled by reused dtype-static type instantiations is zero-cost \newterm{tag-structures}. … … 815 815 \subsection{Member Access} 816 816 817 It is also possible to access multiple members from a single expression using a \newterm{member-access}.817 It is also possible to access multiple fields from a single expression using a \newterm{member-access}. 818 818 The result is a single tuple-valued expression whose type is the tuple of the types of the members, \eg: 819 819 \begin{cfa} … … 1020 1020 \begin{cfa} 1021 1021 forall( dtype T0, dtype T1 | sized(T0) | sized(T1) ) struct _tuple2 { 1022 T0 member_0; T1 member_1; $\C{// generated before the first 2-tuple}$1022 T0 field_0; T1 field_1; $\C{// generated before the first 2-tuple}$ 1023 1023 }; 1024 1024 _tuple2(int, int) f() { 1025 1025 _tuple2(double, double) x; 1026 1026 forall( dtype T0, dtype T1, dtype T2 | sized(T0) | sized(T1) | sized(T2) ) struct _tuple3 { 1027 T0 member_0; T1 member_1; T2 member_2; $\C{// generated before the first 3-tuple}$1027 T0 field_0; T1 field_1; T2 field_2; $\C{// generated before the first 3-tuple}$ 1028 1028 }; 1029 1029 _tuple3(int, double, int) y; … … 1033 1033 1034 1034 \begin{comment} 1035 Since tuples are essentially structures, tuple indexing expressions are just memberaccesses:1035 Since tuples are essentially structures, tuple indexing expressions are just field accesses: 1036 1036 \begin{cfa} 1037 1037 void f(int, [double, char]); … … 1047 1047 _tuple2(int, double) x; 1048 1048 1049 x. member_0+x.member_1;1050 printf("%d %g\n", x. member_0, x.member_1);1051 f(x. member_0, (_tuple2){ x.member_1, 'z' });1052 \end{cfa} 1053 Note that due to flattening, @x@ used in the argument position is converted into the list of its members.1049 x.field_0+x.field_1; 1050 printf("%d %g\n", x.field_0, x.field_1); 1051 f(x.field_0, (_tuple2){ x.field_1, 'z' }); 1052 \end{cfa} 1053 Note that due to flattening, @x@ used in the argument position is converted into the list of its fields. 1054 1054 In the call to @f@, the second and third argument components are structured into a tuple argument. 1055 1055 Similarly, tuple member expressions are recursively expanded into a list of member access expressions. … … 1083 1083 1084 1084 The various kinds of tuple assignment, constructors, and destructors generate GNU C statement expressions. 1085 A variable is generated to store the value produced by a statement expression, since its members may need to be constructed with a non-trivial constructor and it may need to be referred to multiple time, \eg in a unique expression.1085 A variable is generated to store the value produced by a statement expression, since its fields may need to be constructed with a non-trivial constructor and it may need to be referred to multiple time, \eg in a unique expression. 1086 1086 The use of statement expressions allows the translator to arbitrarily generate additional temporary variables as needed, but binds the implementation to a non-standard extension of the C language. 1087 1087 However, there are other places where the \CFA translator makes use of GNU C extensions, such as its use of nested functions, so this restriction is not new. … … 1493 1493 1494 1494 Heterogeneous data is often aggregated into a structure/union. 1495 To reduce syntactic noise, \CFA provides a @with@ statement (see Pascal~\cite[\S~4.F]{Pascal}) to elide aggregate member-qualification by opening a scope containing the memberidentifiers.1495 To reduce syntactic noise, \CFA provides a @with@ statement (see Pascal~\cite[\S~4.F]{Pascal}) to elide aggregate field-qualification by opening a scope containing the field identifiers. 1496 1496 \begin{cquote} 1497 1497 \vspace*{-\baselineskip}%??? … … 1530 1530 The type must be an aggregate type. 1531 1531 (Enumerations are already opened.) 1532 The object is the implicit qualifier for the open structure- members.1532 The object is the implicit qualifier for the open structure-fields. 1533 1533 1534 1534 All expressions in the expression list are open in parallel within the compound statement, which is different from Pascal, which nests the openings from left to right. 1535 The difference between parallel and nesting occurs for members with the same name and type:1536 \begin{cfa} 1537 struct S { int `i`; int j; double m; } s, w; $\C{// member i has same type in structure types S and T}$1535 The difference between parallel and nesting occurs for fields with the same name and type: 1536 \begin{cfa} 1537 struct S { int `i`; int j; double m; } s, w; 1538 1538 struct T { int `i`; int k; int m; } t, w; 1539 with ( s, t ) { $\C{// open structure variables s and t in parallel}$1539 with ( s, t ) { 1540 1540 j + k; $\C{// unambiguous, s.j + t.k}$ 1541 1541 m = 5.0; $\C{// unambiguous, s.m = 5.0}$ … … 1549 1549 For parallel semantics, both @s.i@ and @t.i@ are visible, so @i@ is ambiguous without qualification; 1550 1550 for nested semantics, @t.i@ hides @s.i@, so @i@ implies @t.i@. 1551 \CFA's ability to overload variables means members with the same name but different types are automatically disambiguated, eliminating most qualification when opening multiple aggregates.1551 \CFA's ability to overload variables means fields with the same name but different types are automatically disambiguated, eliminating most qualification when opening multiple aggregates. 1552 1552 Qualification or a cast is used to disambiguate. 1553 1553 … … 1555 1555 \begin{cfa} 1556 1556 void ?{}( S & s, int i ) with ( s ) { $\C{// constructor}$ 1557 `s.i = i;` j = 3; m = 5.5; $\C{// initialize members}$1557 `s.i = i;` j = 3; m = 5.5; $\C{// initialize fields}$ 1558 1558 } 1559 1559 \end{cfa} … … 1659 1659 \lstMakeShortInline@% 1660 1660 \end{cquote} 1661 The only exception is bit -field specification, which always appear to the right of the base type.1661 The only exception is bit field specification, which always appear to the right of the base type. 1662 1662 % Specifically, the character @*@ is used to indicate a pointer, square brackets @[@\,@]@ are used to represent an array or function return value, and parentheses @()@ are used to indicate a function parameter. 1663 1663 However, unlike C, \CFA type declaration tokens are distributed across all variables in the declaration list. … … 1715 1715 // pointer to array of 5 doubles 1716 1716 1717 // common bit -field syntax1717 // common bit field syntax 1718 1718 1719 1719 … … 1911 1911 \subsection{Type Nesting} 1912 1912 1913 Nested types provide a mechanism to organize associated types and refactor a subset of members into a named aggregate (\eg sub-aggregates @name@, @address@, @department@, within aggregate @employe@).1913 Nested types provide a mechanism to organize associated types and refactor a subset of fields into a named aggregate (\eg sub-aggregates @name@, @address@, @department@, within aggregate @employe@). 1914 1914 Java nested types are dynamic (apply to objects), \CC are static (apply to the \lstinline[language=C++]@class@), and C hoists (refactors) nested types into the enclosing scope, meaning there is no need for type qualification. 1915 1915 Since \CFA in not object-oriented, adopting dynamic scoping does not make sense; 1916 instead \CFA adopts \CC static nesting, using the member-selection operator ``@.@'' for type qualification, as does Java, rather than the \CC type-selection operator ``@::@'' (see Figure~\ref{f:TypeNestingQualification}).1916 instead \CFA adopts \CC static nesting, using the field-selection operator ``@.@'' for type qualification, as does Java, rather than the \CC type-selection operator ``@::@'' (see Figure~\ref{f:TypeNestingQualification}). 1917 1917 \begin{figure} 1918 1918 \centering … … 2005 2005 Destruction parameters are useful for specifying storage-management actions, such as de-initialize but not deallocate.}. 2006 2006 \begin{cfa} 2007 struct VLA { int size, * data; }; $\C{// variable length array of integers}$2008 void ?{}( VLA & vla ) with ( vla ) { size = 10; data = alloc( size); } $\C{// default constructor}$2007 struct VLA { int len, * data; }; $\C{// variable length array of integers}$ 2008 void ?{}( VLA & vla ) with ( vla ) { len = 10; data = alloc( len ); } $\C{// default constructor}$ 2009 2009 void ^?{}( VLA & vla ) with ( vla ) { free( data ); } $\C{// destructor}$ 2010 2010 { … … 2013 2013 \end{cfa} 2014 2014 @VLA@ is a \newterm{managed type}\footnote{ 2015 A managed type affects the runtime environment versus a self-contained type.}: a type requiring a non-trivial constructor or destructor, or with a memberof a managed type.2015 A managed type affects the runtime environment versus a self-contained type.}: a type requiring a non-trivial constructor or destructor, or with a field of a managed type. 2016 2016 A managed type is implicitly constructed at allocation and destructed at deallocation to ensure proper interaction with runtime resources, in this case, the @data@ array in the heap. 2017 2017 For details of the code-generation placement of implicit constructor and destructor calls among complex executable statements see~\cite[\S~2.2]{Schluntz17}. … … 2019 2019 \CFA also provides syntax for \newterm{initialization} and \newterm{copy}: 2020 2020 \begin{cfa} 2021 void ?{}( VLA & vla, int size, char fill = '\0') { $\C{// initialization}$2022 vla.[ size, data ] = [ size, alloc( size, fill ) ];2021 void ?{}( VLA & vla, int size, char fill ) with ( vla ) { $\C{// initialization}$ 2022 len = size; data = alloc( len, fill ); 2023 2023 } 2024 2024 void ?{}( VLA & vla, VLA other ) { $\C{// copy, shallow}$ 2025 vla = other;2025 vla.len = other.len; vla.data = other.data; 2026 2026 } 2027 2027 \end{cfa} … … 2036 2036 2037 2037 \CFA constructors may be explicitly called, like Java, and destructors may be explicitly called, like \CC. 2038 Explicit calls to constructors double as a \CC-style \emph{placement syntax}, useful for construction of member s in user-defined constructors and reuse of existing storage allocations.2038 Explicit calls to constructors double as a \CC-style \emph{placement syntax}, useful for construction of member fields in user-defined constructors and reuse of existing storage allocations. 2039 2039 Like the other operators in \CFA, there is a concise syntax for constructor/destructor function calls: 2040 2040 \begin{cfa} … … 2048 2048 y{ x }; $\C{// reallocate y, points to x}$ 2049 2049 x{}; $\C{// reallocate x, not pointing to y}$ 2050 } // ^z{}; ^y{}; ^x{}; 2050 // ^z{}; ^y{}; ^x{}; 2051 } 2051 2052 \end{cfa} 2052 2053 … … 2059 2060 For compatibility with C, a copy constructor from the first union member type is also defined. 2060 2061 For @struct@ types, each of the four functions are implicitly defined to call their corresponding functions on each member of the struct. 2061 To better simulate the behaviour of C initializers, a set of \newterm{ memberconstructors} is also generated for structures.2062 To better simulate the behaviour of C initializers, a set of \newterm{field constructors} is also generated for structures. 2062 2063 A constructor is generated for each non-empty prefix of a structure's member-list to copy-construct the members passed as parameters and default-construct the remaining members. 2063 To allow users to limit the set of constructors available for a type, when a user declares any constructor or destructor, the corresponding generated function and all memberconstructors for that type are hidden from expression resolution;2064 To allow users to limit the set of constructors available for a type, when a user declares any constructor or destructor, the corresponding generated function and all field constructors for that type are hidden from expression resolution; 2064 2065 similarly, the generated default constructor is hidden upon declaration of any constructor. 2065 2066 These semantics closely mirror the rule for implicit declaration of constructors in \CC\cite[p.~186]{ANSI98:C++}. … … 2739 2740 2740 2741 \section{Related Work} 2741 \label{s:RelatedWork}2742 2742 2743 2743 … … 2793 2793 C provides variadic functions through @va_list@ objects, but the programmer is responsible for managing the number of arguments and their types, so the mechanism is type unsafe. 2794 2794 KW-C~\cite{Buhr94a}, a predecessor of \CFA, introduced tuples to C as an extension of the C syntax, taking much of its inspiration from SETL. 2795 The main contributions of that work were adding MRVF, tuple mass and multiple assignment, and record- memberaccess.2795 The main contributions of that work were adding MRVF, tuple mass and multiple assignment, and record-field access. 2796 2796 \CCeleven introduced @std::tuple@ as a library variadic template structure. 2797 2797 Tuples are a generalization of @std::pair@, in that they allow for arbitrary length, fixed-size aggregation of heterogeneous values. -
src/Parser/parser.yy
r8dbedfc r13073be 10 10 // Created On : Sat Sep 1 20:22:55 2001 11 11 // Last Modified By : Peter A. Buhr 12 // Last Modified On : T hu May 24 18:11:59201813 // Update Count : 33 6912 // Last Modified On : Tue May 22 08:41:57 2018 13 // Update Count : 3353 14 14 // 15 15 … … 837 837 // '[' push assignment_expression pop ']' 838 838 // { $$ = new ExpressionNode( build_tuple( $3 ) ); } 839 '[' push ',' tuple_expression_list pop']'840 { $$ = new ExpressionNode( build_tuple( (ExpressionNode *)(new ExpressionNode( nullptr ) )->set_last( $ 4) ) ); }841 | '[' push assignment_expression ',' tuple_expression_list pop']'842 { $$ = new ExpressionNode( build_tuple( (ExpressionNode *)$ 3->set_last( $5) ) ); }839 '[' ',' tuple_expression_list ']' 840 { $$ = new ExpressionNode( build_tuple( (ExpressionNode *)(new ExpressionNode( nullptr ) )->set_last( $3 ) ) ); } 841 | '[' assignment_expression ',' tuple_expression_list ']' 842 { $$ = new ExpressionNode( build_tuple( (ExpressionNode *)$2->set_last( $4 ) ) ); } 843 843 ; 844 844 … … 866 866 labeled_statement 867 867 | compound_statement 868 | expression_statement 868 | expression_statement { $$ = $1; } 869 869 | selection_statement 870 870 | iteration_statement … … 1183 1183 type_specifier_nobody 1184 1184 | type_specifier_nobody declarator 1185 { $$ = $2->addType( $1 ); } 1185 { 1186 $$ = $2->addType( $1 ); 1187 } 1186 1188 | type_specifier_nobody variable_abstract_declarator 1187 1189 { $$ = $2->addType( $1 ); } 1188 1190 | cfa_abstract_declarator_tuple no_attr_identifier // CFA 1189 { $$ = $1->addName( $2 ); } 1191 { 1192 $$ = $1->addName( $2 ); 1193 } 1190 1194 | cfa_abstract_declarator_tuple // CFA 1191 1195 ; … … 1265 1269 1266 1270 declaration_list_opt: // used at beginning of switch statement 1267 pop // empty1271 pop 1268 1272 { $$ = nullptr; } 1269 1273 | declaration_list … … 1300 1304 1301 1305 local_label_list: // GCC, local label 1302 no_attr_identifier_or_type_name 1303 | local_label_list ',' no_attr_identifier_or_type_name 1306 no_attr_identifier_or_type_name {} 1307 | local_label_list ',' no_attr_identifier_or_type_name {} 1304 1308 ; 1305 1309 … … 1396 1400 // type_specifier can resolve to just TYPEDEFname (e.g., typedef int T; int f( T );). Therefore this must be 1397 1401 // flattened to allow lookahead to the '(' without having to reduce identifier_or_type_name. 1398 cfa_abstract_tuple identifier_or_type_name '(' push cfa_parameter_type_list_opt pop')'1402 cfa_abstract_tuple identifier_or_type_name '(' cfa_parameter_type_list_opt ')' 1399 1403 // To obtain LR(1 ), this rule must be factored out from function return type (see cfa_abstract_declarator). 1400 { $$ = DeclarationNode::newFunction( $2, $1, $ 5, 0 ); }1401 | cfa_function_return identifier_or_type_name '(' push cfa_parameter_type_list_opt pop')'1402 { $$ = DeclarationNode::newFunction( $2, $1, $ 5, 0 ); }1404 { $$ = DeclarationNode::newFunction( $2, $1, $4, 0 ); } 1405 | cfa_function_return identifier_or_type_name '(' cfa_parameter_type_list_opt ')' 1406 { $$ = DeclarationNode::newFunction( $2, $1, $4, 0 ); } 1403 1407 ; 1404 1408 1405 1409 cfa_function_return: // CFA 1406 '[' push cfa_parameter_list pop ']' 1407 { $$ = DeclarationNode::newTuple( $3 ); } 1408 | '[' push cfa_parameter_list pop ',' push cfa_abstract_parameter_list pop ']' 1409 // To obtain LR(1 ), the last cfa_abstract_parameter_list is added into this flattened rule to lookahead to the ']'. 1410 { $$ = DeclarationNode::newTuple( $3->appendList( $7 ) ); } 1410 '[' cfa_parameter_list ']' 1411 { $$ = DeclarationNode::newTuple( $2 ); } 1412 | '[' cfa_parameter_list ',' cfa_abstract_parameter_list ']' 1413 // To obtain LR(1 ), the last cfa_abstract_parameter_list is added into this flattened rule to lookahead to the 1414 // ']'. 1415 { $$ = DeclarationNode::newTuple( $2->appendList( $4 ) ); } 1411 1416 ; 1412 1417 … … 1582 1587 1583 1588 forall: 1584 FORALL '(' push type_parameter_list pop ')' // CFA 1585 { $$ = DeclarationNode::newForall( $4 ); } 1589 FORALL '(' 1590 { 1591 typedefTable.enterScope(); 1592 } 1593 type_parameter_list ')' // CFA 1594 { 1595 typedefTable.leaveScope(); 1596 $$ = DeclarationNode::newForall( $4 ); 1597 } 1586 1598 ; 1587 1599 … … 1958 1970 | cfa_abstract_parameter_list 1959 1971 | cfa_parameter_list 1960 | cfa_parameter_list pop ',' pushcfa_abstract_parameter_list1961 { $$ = $1->appendList( $ 5); }1962 | cfa_abstract_parameter_list pop ',' pushELLIPSIS1972 | cfa_parameter_list ',' cfa_abstract_parameter_list 1973 { $$ = $1->appendList( $3 ); } 1974 | cfa_abstract_parameter_list ',' ELLIPSIS 1963 1975 { $$ = $1->addVarArgs(); } 1964 | cfa_parameter_list pop ',' pushELLIPSIS1976 | cfa_parameter_list ',' ELLIPSIS 1965 1977 { $$ = $1->addVarArgs(); } 1966 1978 ; … … 1970 1982 // factored out from cfa_parameter_list, flattening the rules to get lookahead to the ']'. 1971 1983 cfa_parameter_declaration 1972 | cfa_abstract_parameter_list pop ',' pushcfa_parameter_declaration1973 { $$ = $1->appendList( $ 5); }1974 | cfa_parameter_list pop ',' pushcfa_parameter_declaration1975 { $$ = $1->appendList( $ 5); }1976 | cfa_parameter_list pop ',' push cfa_abstract_parameter_list pop ',' pushcfa_parameter_declaration1977 { $$ = $1->appendList( $ 5 )->appendList( $9); }1984 | cfa_abstract_parameter_list ',' cfa_parameter_declaration 1985 { $$ = $1->appendList( $3 ); } 1986 | cfa_parameter_list ',' cfa_parameter_declaration 1987 { $$ = $1->appendList( $3 ); } 1988 | cfa_parameter_list ',' cfa_abstract_parameter_list ',' cfa_parameter_declaration 1989 { $$ = $1->appendList( $3 )->appendList( $5 ); } 1978 1990 ; 1979 1991 1980 1992 cfa_abstract_parameter_list: // CFA, new & old style abstract 1981 1993 cfa_abstract_parameter_declaration 1982 | cfa_abstract_parameter_list pop ',' pushcfa_abstract_parameter_declaration1983 { $$ = $1->appendList( $ 5); }1994 | cfa_abstract_parameter_list ',' cfa_abstract_parameter_declaration 1995 { $$ = $1->appendList( $3 ); } 1984 1996 ; 1985 1997 … … 2130 2142 '.' no_attr_identifier // C99, field name 2131 2143 { $$ = new ExpressionNode( build_varref( $2 ) ); } 2132 | '[' push assignment_expression pop ']'// C99, single array element2144 | '[' assignment_expression ']' // C99, single array element 2133 2145 // assignment_expression used instead of constant_expression because of shift/reduce conflicts with tuple. 2146 { $$ = $2; } 2147 | '[' subrange ']' // CFA, multiple array elements 2148 { $$ = $2; } 2149 | '[' constant_expression ELLIPSIS constant_expression ']' // GCC, multiple array elements 2150 { $$ = new ExpressionNode( new RangeExpr( maybeMoveBuild< Expression >( $2 ), maybeMoveBuild< Expression >( $4 ) ) ); } 2151 | '.' '[' field_list ']' // CFA, tuple field selector 2134 2152 { $$ = $3; } 2135 | '[' push subrange pop ']' // CFA, multiple array elements2136 { $$ = $3; }2137 | '[' push constant_expression ELLIPSIS constant_expression pop ']' // GCC, multiple array elements2138 { $$ = new ExpressionNode( new RangeExpr( maybeMoveBuild< Expression >( $3 ), maybeMoveBuild< Expression >( $5 ) ) ); }2139 | '.' '[' push field_list pop ']' // CFA, tuple field selector2140 { $$ = $4; }2141 2153 ; 2142 2154 … … 2257 2269 TRAIT no_attr_identifier_or_type_name '(' push type_parameter_list pop ')' '{' '}' 2258 2270 { $$ = DeclarationNode::newTrait( $2, $5, 0 ); } 2259 | TRAIT no_attr_identifier_or_type_name '(' push type_parameter_list pop ')' '{' push trait_declaration_list '}' 2271 | TRAIT no_attr_identifier_or_type_name '(' push type_parameter_list pop ')' '{' 2272 { typedefTable.enterScope(); } 2273 trait_declaration_list '}' 2260 2274 { $$ = DeclarationNode::newTrait( $2, $5, $10 ); } 2261 2275 ; … … 2274 2288 cfa_trait_declaring_list: // CFA 2275 2289 cfa_variable_specifier 2290 { $$ = $1; } 2276 2291 | cfa_function_specifier 2292 { $$ = $1; } 2277 2293 | cfa_trait_declaring_list pop ',' push identifier_or_type_name 2278 2294 { $$ = $1->appendList( $1->cloneType( $5 ) ); } … … 2333 2349 } 2334 2350 | type_qualifier_list 2335 { if ( $1->type->forall ) xxx = forall = true; } // remember generic type 2351 { 2352 if ( $1->type->forall ) xxx = forall = true; // remember generic type 2353 } 2336 2354 push '{' external_definition_list '}' // CFA, namespace 2337 2355 { … … 2346 2364 } 2347 2365 | declaration_qualifier_list 2348 { if ( $1->type->forall ) xxx = forall = true; } // remember generic type 2366 { 2367 if ( $1->type->forall ) xxx = forall = true; // remember generic type 2368 } 2349 2369 push '{' external_definition_list '}' // CFA, namespace 2350 2370 { … … 2386 2406 // declaration must still have a type_specifier. OBSOLESCENT (see 1) 2387 2407 | function_declarator compound_statement 2388 { $$ = $1->addFunctionBody( $2 ); } 2408 { 2409 typedefTable.leaveScope(); 2410 $$ = $1->addFunctionBody( $2 ); 2411 } 2389 2412 | KR_function_declarator KR_declaration_list_opt compound_statement 2390 { $$ = $1->addOldDeclList( $2 )->addFunctionBody( $3 ); } 2413 { 2414 typedefTable.leaveScope(); 2415 $$ = $1->addOldDeclList( $2 )->addFunctionBody( $3 ); 2416 } 2391 2417 ; 2392 2418 … … 2401 2427 cfa_function_declaration with_clause_opt compound_statement // CFA 2402 2428 { 2429 typedefTable.leaveScope(); 2403 2430 // Add the function body to the last identifier in the function definition list, i.e., foo3: 2404 2431 // [const double] foo1(), foo2( int ), foo3( double ) { return 3.0; } … … 2409 2436 { 2410 2437 rebindForall( $1, $2 ); 2438 typedefTable.leaveScope(); 2411 2439 $$ = $2->addFunctionBody( $4, $3 )->addType( $1 ); 2412 2440 } … … 2414 2442 { 2415 2443 rebindForall( $1, $2 ); 2444 typedefTable.leaveScope(); 2416 2445 $$ = $2->addFunctionBody( $4, $3 )->addType( $1 ); 2417 2446 } 2418 2447 // handles default int return type, OBSOLESCENT (see 1) 2419 2448 | type_qualifier_list function_declarator with_clause_opt compound_statement 2420 { $$ = $2->addFunctionBody( $4, $3 )->addQualifiers( $1 ); } 2449 { 2450 typedefTable.leaveScope(); 2451 $$ = $2->addFunctionBody( $4, $3 )->addQualifiers( $1 ); 2452 } 2421 2453 // handles default int return type, OBSOLESCENT (see 1) 2422 2454 | declaration_qualifier_list function_declarator with_clause_opt compound_statement 2423 { $$ = $2->addFunctionBody( $4, $3 )->addQualifiers( $1 ); } 2455 { 2456 typedefTable.leaveScope(); 2457 $$ = $2->addFunctionBody( $4, $3 )->addQualifiers( $1 ); 2458 } 2424 2459 // handles default int return type, OBSOLESCENT (see 1) 2425 2460 | declaration_qualifier_list type_qualifier_list function_declarator with_clause_opt compound_statement 2426 { $$ = $3->addFunctionBody( $5, $4 )->addQualifiers( $2 )->addQualifiers( $1 ); } 2461 { 2462 typedefTable.leaveScope(); 2463 $$ = $3->addFunctionBody( $5, $4 )->addQualifiers( $2 )->addQualifiers( $1 ); 2464 } 2427 2465 2428 2466 // Old-style K&R function definition, OBSOLESCENT (see 4) … … 2430 2468 { 2431 2469 rebindForall( $1, $2 ); 2470 typedefTable.leaveScope(); 2432 2471 $$ = $2->addOldDeclList( $3 )->addFunctionBody( $5, $4 )->addType( $1 ); 2433 2472 } 2434 2473 // handles default int return type, OBSOLESCENT (see 1) 2435 2474 | type_qualifier_list KR_function_declarator KR_declaration_list_opt with_clause_opt compound_statement 2436 { $$ = $2->addOldDeclList( $3 )->addFunctionBody( $5, $4 )->addQualifiers( $1 ); } 2475 { 2476 typedefTable.leaveScope(); 2477 $$ = $2->addOldDeclList( $3 )->addFunctionBody( $5, $4 )->addQualifiers( $1 ); 2478 } 2437 2479 // handles default int return type, OBSOLESCENT (see 1) 2438 2480 | declaration_qualifier_list KR_function_declarator KR_declaration_list_opt with_clause_opt compound_statement 2439 { $$ = $2->addOldDeclList( $3 )->addFunctionBody( $5, $4 )->addQualifiers( $1 ); } 2481 { 2482 typedefTable.leaveScope(); 2483 $$ = $2->addOldDeclList( $3 )->addFunctionBody( $5, $4 )->addQualifiers( $1 ); 2484 } 2440 2485 // handles default int return type, OBSOLESCENT (see 1) 2441 2486 | declaration_qualifier_list type_qualifier_list KR_function_declarator KR_declaration_list_opt with_clause_opt compound_statement 2442 { $$ = $3->addOldDeclList( $4 )->addFunctionBody( $6, $5 )->addQualifiers( $2 )->addQualifiers( $1 ); } 2487 { 2488 typedefTable.leaveScope(); 2489 $$ = $3->addOldDeclList( $4 )->addFunctionBody( $6, $5 )->addQualifiers( $2 )->addQualifiers( $1 ); 2490 } 2443 2491 ; 2444 2492 … … 2637 2685 paren_identifier '(' identifier_list ')' // function_declarator handles empty parameter 2638 2686 { $$ = $1->addIdList( $3 ); } 2639 | '(' KR_function_ptr ')' '(' p ush parameter_type_list_opt pop')'2640 { $$ = $2->addParamList( $ 6); }2687 | '(' KR_function_ptr ')' '(' parameter_type_list_opt ')' 2688 { $$ = $2->addParamList( $5 ); } 2641 2689 | '(' KR_function_no_ptr ')' // redundant parenthesis 2642 2690 { $$ = $2; } … … 2756 2804 2757 2805 identifier_parameter_function: 2758 paren_identifier '(' p ush parameter_type_list_opt pop ')'// empty parameter list OBSOLESCENT (see 3)2759 { $$ = $1->addParamList( $ 4); }2760 | '(' identifier_parameter_ptr ')' '(' p ush parameter_type_list_opt pop')' // empty parameter list OBSOLESCENT (see 3)2761 { $$ = $2->addParamList( $ 6); }2806 paren_identifier '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 2807 { $$ = $1->addParamList( $3 ); } 2808 | '(' identifier_parameter_ptr ')' '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 2809 { $$ = $2->addParamList( $5 ); } 2762 2810 | '(' identifier_parameter_function ')' // redundant parenthesis 2763 2811 { $$ = $2; } … … 2809 2857 2810 2858 type_parameter_function: 2811 typedef '(' p ush parameter_type_list_opt pop ')'// empty parameter list OBSOLESCENT (see 3)2812 { $$ = $1->addParamList( $ 4); }2813 | '(' type_parameter_ptr ')' '(' p ush parameter_type_list_opt pop')' // empty parameter list OBSOLESCENT (see 3)2814 { $$ = $2->addParamList( $ 6); }2859 typedef '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 2860 { $$ = $1->addParamList( $3 ); } 2861 | '(' type_parameter_ptr ')' '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 2862 { $$ = $2->addParamList( $5 ); } 2815 2863 ; 2816 2864 … … 2859 2907 2860 2908 abstract_function: 2861 '(' p ush parameter_type_list_opt pop ')'// empty parameter list OBSOLESCENT (see 3)2862 { $$ = DeclarationNode::newFunction( nullptr, nullptr, $ 3, nullptr ); }2863 | '(' abstract_ptr ')' '(' p ush parameter_type_list_opt pop')' // empty parameter list OBSOLESCENT (see 3)2864 { $$ = $2->addParamList( $ 6); }2909 '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 2910 { $$ = DeclarationNode::newFunction( nullptr, nullptr, $2, nullptr ); } 2911 | '(' abstract_ptr ')' '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 2912 { $$ = $2->addParamList( $5 ); } 2865 2913 | '(' abstract_function ')' // redundant parenthesis 2866 2914 { $$ = $2; } … … 2877 2925 2878 2926 multi_array_dimension: 2879 '[' push assignment_expression pop']'2880 { $$ = DeclarationNode::newArray( $ 3, 0, false ); }2881 | '[' push '*' pop ']'// C992927 '[' assignment_expression ']' 2928 { $$ = DeclarationNode::newArray( $2, 0, false ); } 2929 | '[' '*' ']' // C99 2882 2930 { $$ = DeclarationNode::newVarArray( 0 ); } 2883 | multi_array_dimension '[' push assignment_expression pop']'2884 { $$ = $1->addArray( DeclarationNode::newArray( $ 4, 0, false ) ); }2885 | multi_array_dimension '[' push '*' pop ']'// C992931 | multi_array_dimension '[' assignment_expression ']' 2932 { $$ = $1->addArray( DeclarationNode::newArray( $3, 0, false ) ); } 2933 | multi_array_dimension '[' '*' ']' // C99 2886 2934 { $$ = $1->addArray( DeclarationNode::newVarArray( 0 ) ); } 2887 2935 ; … … 2950 2998 2951 2999 abstract_parameter_function: 2952 '(' p ush parameter_type_list_opt pop ')'// empty parameter list OBSOLESCENT (see 3)2953 { $$ = DeclarationNode::newFunction( nullptr, nullptr, $ 3, nullptr ); }2954 | '(' abstract_parameter_ptr ')' '(' p ush parameter_type_list_opt pop')' // empty parameter list OBSOLESCENT (see 3)2955 { $$ = $2->addParamList( $ 6); }3000 '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 3001 { $$ = DeclarationNode::newFunction( nullptr, nullptr, $2, nullptr ); } 3002 | '(' abstract_parameter_ptr ')' '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 3003 { $$ = $2->addParamList( $5 ); } 2956 3004 | '(' abstract_parameter_function ')' // redundant parenthesis 2957 3005 { $$ = $2; } … … 2975 3023 { $$ = DeclarationNode::newArray( 0, 0, false ); } 2976 3024 // multi_array_dimension handles the '[' '*' ']' case 2977 | '[' push type_qualifier_list '*' pop ']'// remaining C992978 { $$ = DeclarationNode::newVarArray( $ 3); }2979 | '[' push type_qualifier_list pop']'2980 { $$ = DeclarationNode::newArray( 0, $ 3, false ); }3025 | '[' type_qualifier_list '*' ']' // remaining C99 3026 { $$ = DeclarationNode::newVarArray( $2 ); } 3027 | '[' type_qualifier_list ']' 3028 { $$ = DeclarationNode::newArray( 0, $2, false ); } 2981 3029 // multi_array_dimension handles the '[' assignment_expression ']' case 2982 | '[' push type_qualifier_list assignment_expression pop']'2983 { $$ = DeclarationNode::newArray( $ 4, $3, false ); }2984 | '[' push STATIC type_qualifier_list_opt assignment_expression pop']'2985 { $$ = DeclarationNode::newArray( $ 5, $4, true ); }2986 | '[' push type_qualifier_list STATIC assignment_expression pop']'2987 { $$ = DeclarationNode::newArray( $ 5, $3, true ); }3030 | '[' type_qualifier_list assignment_expression ']' 3031 { $$ = DeclarationNode::newArray( $3, $2, false ); } 3032 | '[' STATIC type_qualifier_list_opt assignment_expression ']' 3033 { $$ = DeclarationNode::newArray( $4, $3, true ); } 3034 | '[' type_qualifier_list STATIC assignment_expression ']' 3035 { $$ = DeclarationNode::newArray( $4, $2, true ); } 2988 3036 ; 2989 3037 … … 3029 3077 3030 3078 variable_abstract_function: 3031 '(' variable_abstract_ptr ')' '(' p ush parameter_type_list_opt pop')' // empty parameter list OBSOLESCENT (see 3)3032 { $$ = $2->addParamList( $ 6); }3079 '(' variable_abstract_ptr ')' '(' parameter_type_list_opt ')' // empty parameter list OBSOLESCENT (see 3) 3080 { $$ = $2->addParamList( $5 ); } 3033 3081 | '(' variable_abstract_function ')' // redundant parenthesis 3034 3082 { $$ = $2; } … … 3093 3141 3094 3142 cfa_array_parameter_1st_dimension: 3095 '[' push type_qualifier_list '*' pop ']'// remaining C993096 { $$ = DeclarationNode::newVarArray( $ 3); }3097 | '[' push type_qualifier_list assignment_expression pop']'3098 { $$ = DeclarationNode::newArray( $ 4, $3, false ); }3099 | '[' push declaration_qualifier_list assignment_expression pop']'3143 '[' type_qualifier_list '*' ']' // remaining C99 3144 { $$ = DeclarationNode::newVarArray( $2 ); } 3145 | '[' type_qualifier_list assignment_expression ']' 3146 { $$ = DeclarationNode::newArray( $3, $2, false ); } 3147 | '[' declaration_qualifier_list assignment_expression ']' 3100 3148 // declaration_qualifier_list must be used because of shift/reduce conflict with 3101 3149 // assignment_expression, so a semantic check is necessary to preclude them as a type_qualifier cannot 3102 3150 // appear in this context. 3103 { $$ = DeclarationNode::newArray( $ 4, $3, true ); }3104 | '[' push declaration_qualifier_list type_qualifier_list assignment_expression pop']'3105 { $$ = DeclarationNode::newArray( $ 5, $4->addQualifiers( $3 ), true ); }3151 { $$ = DeclarationNode::newArray( $3, $2, true ); } 3152 | '[' declaration_qualifier_list type_qualifier_list assignment_expression ']' 3153 { $$ = DeclarationNode::newArray( $4, $3->addQualifiers( $3 ), true ); } 3106 3154 ; 3107 3155 … … 3172 3220 3173 3221 cfa_abstract_tuple: // CFA 3174 '[' push cfa_abstract_parameter_list pop']'3175 { $$ = DeclarationNode::newTuple( $ 3); }3222 '[' cfa_abstract_parameter_list ']' 3223 { $$ = DeclarationNode::newTuple( $2 ); } 3176 3224 ; 3177 3225 … … 3179 3227 // '[' ']' '(' cfa_parameter_type_list_opt ')' 3180 3228 // { $$ = DeclarationNode::newFunction( nullptr, DeclarationNode::newTuple( nullptr ), $4, nullptr ); } 3181 cfa_abstract_tuple '(' push cfa_parameter_type_list_opt pop')'3182 { $$ = DeclarationNode::newFunction( nullptr, $1, $ 4, nullptr ); }3183 | cfa_function_return '(' push cfa_parameter_type_list_opt pop')'3184 { $$ = DeclarationNode::newFunction( nullptr, $1, $ 4, nullptr ); }3229 cfa_abstract_tuple '(' cfa_parameter_type_list_opt ')' 3230 { $$ = DeclarationNode::newFunction( nullptr, $1, $3, nullptr ); } 3231 | cfa_function_return '(' cfa_parameter_type_list_opt ')' 3232 { $$ = DeclarationNode::newFunction( nullptr, $1, $3, nullptr ); } 3185 3233 ; 3186 3234 -
src/ResolvExpr/AlternativeFinder.cc
r8dbedfc r13073be 698 698 const ExplodedArgs& args, std::vector<ArgPack>& results, std::size_t& genStart, 699 699 const SymTab::Indexer& indexer, unsigned nTuples = 0 ) { 700 if ( TupleType * tupleType = dynamic_cast<TupleType*>( formalType ) ) {700 if ( TupleType* tupleType = dynamic_cast<TupleType*>( formalType ) ) { 701 701 // formalType is a TupleType - group actuals into a TupleExpr 702 702 ++nTuples; 703 703 for ( Type* type : *tupleType ) { 704 704 // xxx - dropping initializer changes behaviour from previous, but seems correct 705 // ^^^ need to handle the case where a tuple has a default argument706 705 if ( ! instantiateArgument( 707 706 type, nullptr, args, results, genStart, indexer, nTuples ) ) … … 714 713 } 715 714 return true; 716 } else if ( TypeInstType * ttype = Tuples::isTtype( formalType ) ) {715 } else if ( TypeInstType* ttype = Tuples::isTtype( formalType ) ) { 717 716 // formalType is a ttype, consumes all remaining arguments 718 717 // xxx - mixing default arguments with variadic?? … … 917 916 // consider only first exploded actual 918 917 Expression* expr = expl.exprs.front().get(); 919 Type* actualType = expr-> result->clone();918 Type* actualType = expr->get_result()->clone(); 920 919 921 920 PRINT( … … 948 947 ApplicationExpr *appExpr = new ApplicationExpr( func.expr->clone() ); 949 948 // sum cost and accumulate actuals 950 std::list<Expression*>& args = appExpr-> args;949 std::list<Expression*>& args = appExpr->get_args(); 951 950 Cost cost = func.cost; 952 951 const ArgPack* pack = &result; … … 975 974 // add all type variables as open variables now so that those not used in the parameter 976 975 // list are still considered open. 977 funcEnv.add( funcType-> forall);978 979 if ( targetType && ! targetType->isVoid() && ! funcType-> returnVals.empty() ) {976 funcEnv.add( funcType->get_forall() ); 977 978 if ( targetType && ! targetType->isVoid() && ! funcType->get_returnVals().empty() ) { 980 979 // attempt to narrow based on expected target type 981 Type * returnType = funcType-> returnVals.front()->get_type();980 Type * returnType = funcType->get_returnVals().front()->get_type(); 982 981 if ( ! unify( returnType, targetType, funcEnv, funcNeed, funcHave, funcOpenVars, 983 982 indexer ) ) { … … 992 991 std::size_t genStart = 0; 993 992 994 for ( DeclarationWithType* formal : funcType-> parameters) {993 for ( DeclarationWithType* formal : funcType->get_parameters() ) { 995 994 ObjectDecl* obj = strict_dynamic_cast< ObjectDecl* >( formal ); 996 995 if ( ! instantiateArgument( 997 obj-> type, obj->init, args, results, genStart, indexer ) )996 obj->get_type(), obj->get_init(), args, results, genStart, indexer ) ) 998 997 return; 999 998 } … … 1076 1075 void AlternativeFinder::Finder::postvisit( UntypedExpr *untypedExpr ) { 1077 1076 AlternativeFinder funcFinder( indexer, env ); 1078 funcFinder.findWithAdjustment( untypedExpr-> function);1077 funcFinder.findWithAdjustment( untypedExpr->get_function() ); 1079 1078 // if there are no function alternatives, then proceeding is a waste of time. 1080 1079 if ( funcFinder.alternatives.empty() ) return; … … 1121 1120 ) 1122 1121 // check if the type is pointer to function 1123 if ( PointerType *pointer = dynamic_cast< PointerType* >( func->expr-> result->stripReferences() ) ) {1124 if ( FunctionType *function = dynamic_cast< FunctionType* >( pointer-> base) ) {1122 if ( PointerType *pointer = dynamic_cast< PointerType* >( func->expr->get_result()->stripReferences() ) ) { 1123 if ( FunctionType *function = dynamic_cast< FunctionType* >( pointer->get_base() ) ) { 1125 1124 Alternative newFunc( *func ); 1126 1125 referenceToRvalueConversion( newFunc.expr, newFunc.cost ); … … 1128 1127 std::back_inserter( candidates ) ); 1129 1128 } 1130 } else if ( TypeInstType *typeInst = dynamic_cast< TypeInstType* >( func->expr-> result->stripReferences() ) ) { // handle ftype (e.g. *? on function pointer)1129 } else if ( TypeInstType *typeInst = dynamic_cast< TypeInstType* >( func->expr->get_result()->stripReferences() ) ) { // handle ftype (e.g. *? on function pointer) 1131 1130 EqvClass eqvClass; 1132 if ( func->env.lookup( typeInst-> name, eqvClass ) && eqvClass.type ) {1131 if ( func->env.lookup( typeInst->get_name(), eqvClass ) && eqvClass.type ) { 1133 1132 if ( FunctionType *function = dynamic_cast< FunctionType* >( eqvClass.type ) ) { 1134 1133 Alternative newFunc( *func ); … … 1159 1158 // check if type is a pointer to function 1160 1159 if ( PointerType* pointer = dynamic_cast<PointerType*>( 1161 funcOp->expr-> result->stripReferences() ) ) {1160 funcOp->expr->get_result()->stripReferences() ) ) { 1162 1161 if ( FunctionType* function = 1163 dynamic_cast<FunctionType*>( pointer-> base) ) {1162 dynamic_cast<FunctionType*>( pointer->get_base() ) ) { 1164 1163 Alternative newFunc( *funcOp ); 1165 1164 referenceToRvalueConversion( newFunc.expr, newFunc.cost ); … … 1183 1182 PRINT( 1184 1183 ApplicationExpr *appExpr = strict_dynamic_cast< ApplicationExpr* >( withFunc.expr ); 1185 PointerType *pointer = strict_dynamic_cast< PointerType* >( appExpr-> function->result);1186 FunctionType *function = strict_dynamic_cast< FunctionType* >( pointer-> base);1187 std::cerr << "Case +++++++++++++ " << appExpr-> function<< std::endl;1184 PointerType *pointer = strict_dynamic_cast< PointerType* >( appExpr->get_function()->get_result() ); 1185 FunctionType *function = strict_dynamic_cast< FunctionType* >( pointer->get_base() ); 1186 std::cerr << "Case +++++++++++++ " << appExpr->get_function() << std::endl; 1188 1187 std::cerr << "formals are:" << std::endl; 1189 printAll( function-> parameters, std::cerr, 8 );1188 printAll( function->get_parameters(), std::cerr, 8 ); 1190 1189 std::cerr << "actuals are:" << std::endl; 1191 printAll( appExpr-> args, std::cerr, 8 );1190 printAll( appExpr->get_args(), std::cerr, 8 ); 1192 1191 std::cerr << "bindings are:" << std::endl; 1193 1192 withFunc.env.print( std::cerr, 8 ); … … 1230 1229 bool isLvalue( Expression *expr ) { 1231 1230 // xxx - recurse into tuples? 1232 return expr->result && ( expr-> result->get_lvalue() || dynamic_cast< ReferenceType * >( expr->result) );1231 return expr->result && ( expr->get_result()->get_lvalue() || dynamic_cast< ReferenceType * >( expr->get_result() ) ); 1233 1232 } 1234 1233 … … 1292 1291 AssertionSet needAssertions, haveAssertions; 1293 1292 OpenVarSet openVars; 1294 1295 alt.env.extractOpenVars( openVars );1296 1293 1297 1294 // It's possible that a cast can throw away some values in a multiply-valued expression. (An example is a … … 1712 1709 AlternativeFinder finder( indexer, env ); 1713 1710 finder.targetType = toType; 1714 finder.findWithAdjustment( initExpr-> expr);1711 finder.findWithAdjustment( initExpr->get_expr() ); 1715 1712 for ( Alternative & alt : finder.get_alternatives() ) { 1716 1713 TypeEnvironment newEnv( alt.env ); … … 1719 1716 PRINT( 1720 1717 std::cerr << " @ " << toType << " " << initAlt.designation << std::endl; 1721 )1718 ) 1722 1719 // It's possible that a cast can throw away some values in a multiply-valued expression. (An example is a 1723 1720 // cast-to-void, which casts from one value to zero.) Figure out the prefix of the subexpression results 1724 1721 // that are cast directly. The candidate is invalid if it has fewer results than there are types to cast 1725 1722 // to. 1726 int discardedValues = alt.expr-> result->size() - toType->size();1723 int discardedValues = alt.expr->get_result()->size() - toType->size(); 1727 1724 if ( discardedValues < 0 ) continue; 1728 1725 // xxx - may need to go into tuple types and extract relevant types and use unifyList. Note that currently, this does not … … 1731 1728 unify( toType, alt.expr->result, newEnv, needAssertions, haveAssertions, openVars, indexer ); // xxx - do some inspecting on this line... why isn't result bound to initAlt.type?? 1732 1729 1733 Cost thisCost = castCost( alt.expr-> result, toType, indexer, newEnv );1730 Cost thisCost = castCost( alt.expr->get_result(), toType, indexer, newEnv ); 1734 1731 if ( thisCost != Cost::infinity ) { 1735 1732 // count one safe conversion for each value that is thrown away -
src/Tuples/TupleAssignment.cc
r8dbedfc r13073be 231 231 232 232 ResolvExpr::AlternativeFinder finder{ currentFinder.get_indexer(), 233 matcher->compositeEnv }; 234 233 currentFinder.get_environ() }; 235 234 try { 236 235 finder.findWithAdjustment(*i); … … 350 349 ltmp.push_back( lobj ); 351 350 rtmp.push_back( robj ); 352 353 // resolve the cast expression so that rhsAlt return type is bound by the cast type as needed, and transfer the resulting environment354 ResolvExpr::AlternativeFinder finder{ spotter.currentFinder.get_indexer(), compositeEnv };355 finder.findWithAdjustment( rhsAlt.expr );356 assert( finder.get_alternatives().size() == 1 );357 compositeEnv = std::move( finder.get_alternatives().front().env );358 351 } 359 352 tmpDecls.splice( tmpDecls.end(), ltmp ); -
src/libcfa/concurrency/alarm.c
r8dbedfc r13073be 10 10 // Created On : Fri Jun 2 11:31:25 2017 11 11 // Last Modified By : Peter A. Buhr 12 // Last Modified On : Fri May 25 06:25:47201813 // Update Count : 6 712 // Last Modified On : Mon Apr 9 13:36:18 2018 13 // Update Count : 61 14 14 // 15 15 … … 37 37 38 38 void __kernel_set_timer( Duration alarm ) { 39 verifyf(alarm >= 1`us || alarm == 0, "Setting timer to < 1us (% jins)", alarm.tv);39 verifyf(alarm >= 1`us || alarm == 0, "Setting timer to < 1us (%luns)", alarm.tv); 40 40 setitimer( ITIMER_REAL, &(itimerval){ alarm }, NULL ); 41 41 } -
src/tests/.expect/math1.x64.txt
r8dbedfc r13073be 12 12 \ 16 256 13 13 \ 912673 256 64 -64 0.015625 -0.015625 18.3791736799526 0.264715-1.1922i 14 log:0 0 0 0.346574+0.785398i 0.346573590279973+0.785398163397448i 0.346573590279972655+0.78539816339744831i 15 log2:3 3 3 16 log10:2 2 2 17 log1p:0.693147 0.693147180559945 0.693147180559945309 18 ilogb:0 0 0 19 logb:3 3 3 20 sqrt:1 1 1 1.09868+0.45509i 1.09868411346781+0.455089860562227i 1.09868411346780997+0.455089860562227341i 21 cbrt:3 3 3 22 hypot:1.41421 1.4142135623731 1.41421356237309505 -
src/tests/.expect/math1.x86.txt
r8dbedfc r13073be 12 12 \ 16 256 13 13 \ 912673 256 64 -64 0.015625 -0.015625 18.3791736799526 0.264715-1.1922i 14 log:0 0 0 0.346574+0.785398i 0.346573590279973+0.785398163397448i 0.346573590279972655+0.78539816339744831i 15 log2:3 3 3 16 log10:2 2 2 17 log1p:0.693147 0.693147180559945 0.693147180559945309 18 ilogb:0 0 0 19 logb:3 3 3 20 sqrt:1 1 1 1.09868+0.45509i 1.09868411346781+0.455089860562227i 1.09868411346780997+0.455089860562227341i 21 cbrt:3 3 3 22 hypot:1.41421 1.4142135623731 1.41421356237309505 -
src/tests/.expect/math2.x64.txt
r8dbedfc r13073be 1 log:0 0 0 0.346574+0.785398i 0.346573590279973+0.785398163397448i 0.346573590279972655+0.78539816339744831i2 log2:3 3 33 log10:2 2 24 log1p:0.693147 0.693147180559945 0.6931471805599453095 ilogb:0 0 06 logb:3 3 37 sqrt:1 1 1 1.09868+0.45509i 1.09868411346781+0.455089860562227i 1.09868411346780997+0.455089860562227341i8 cbrt:3 3 39 hypot:1.41421 1.4142135623731 1.4142135623730950510 1 sin:0.841471 0.841470984807897 0.841470984807896507 1.29846+0.634964i 1.29845758141598+0.634963914784736i 1.29845758141597729+0.634963914784736108i 11 2 cos:0.540302 0.54030230586814 0.540302305868139717 0.83373-0.988898i 0.833730025131149-0.988897705762865i 0.833730025131149049-0.988897705762865096i … … 15 6 atan:0.785398 0.785398163397448 0.78539816339744831 1.01722+0.402359i 1.01722196789785+0.402359478108525i 1.01722196789785137+0.402359478108525094i 16 7 atan2:0.785398 0.785398163397448 0.78539816339744831 atan:0.785398 0.785398163397448 0.78539816339744831 8 sinh:1.1752 1.1752011936438 1.17520119364380146 0.634964+1.29846i 0.634963914784736+1.29845758141598i 0.634963914784736108+1.29845758141597729i 9 cosh:1.54308 1.54308063481524 1.54308063481524378 0.83373+0.988898i 0.833730025131149+0.988897705762865i 0.833730025131149049+0.988897705762865096i 10 tanh:0.761594 0.761594155955765 0.761594155955764888 1.08392+0.271753i 1.08392332733869+0.271752585319512i 1.08392332733869454+0.271752585319511717i 11 acosh:0 0 0 1.06128+0.904557i 1.06127506190504+0.904556894302381i 1.06127506190503565+0.904556894302381364i 12 asinh:0.881374 0.881373587019543 0.881373587019543025 1.06128+0.666239i 1.06127506190504+0.666239432492515i 1.06127506190503565+0.666239432492515255i 13 atanh:inf inf inf 0.402359+1.01722i 0.402359478108525+1.01722196789785i 0.402359478108525094+1.01722196789785137i 14 erf:0.842701 0.842700792949715 0.842700792949714869 15 erfc:0.157299 0.157299207050285 0.157299207050285131 16 lgamma:1.79176 1.79175946922805 1.791759469228055 17 lgamma:1.79176 1 1.79175946922805 1 1.791759469228055 1 18 tgamma:6 6 6 -
src/tests/.expect/math2.x86.txt
r8dbedfc r13073be 1 log:0 0 0 0.346574+0.785398i 0.346573590279973+0.785398163397448i 0.346573590279972655+0.78539816339744831i2 log2:3 3 33 log10:2 2 24 log1p:0.693147 0.693147180559945 0.6931471805599453095 ilogb:0 0 06 logb:3 3 37 sqrt:1 1 1 1.09868+0.45509i 1.09868411346781+0.455089860562227i 1.09868411346780997+0.455089860562227341i8 cbrt:3 3 39 hypot:1.41421 1.4142135623731 1.4142135623730950510 1 sin:0.841471 0.841470984807897 0.841470984807896507 1.29846+0.634964i 1.29845758141598+0.634963914784736i 1.29845758141597729+0.634963914784736108i 11 2 cos:0.540302 0.54030230586814 0.540302305868139717 0.83373-0.988898i 0.833730025131149-0.988897705762865i 0.833730025131149049-0.988897705762865096i … … 15 6 atan:0.785398 0.785398163397448 0.78539816339744831 1.01722+0.402359i 1.01722196789785+0.402359478108525i 1.01722196789785137+0.402359478108525094i 16 7 atan2:0.785398 0.785398163397448 0.78539816339744831 atan:0.785398 0.785398163397448 0.78539816339744831 8 sinh:1.1752 1.1752011936438 1.17520119364380146 0.634964+1.29846i 0.634963914784736+1.29845758141598i 0.634963914784736108+1.29845758141597729i 9 cosh:1.54308 1.54308063481524 1.54308063481524378 0.83373+0.988898i 0.833730025131149+0.988897705762865i 0.833730025131149049+0.988897705762865096i 10 tanh:0.761594 0.761594155955765 0.761594155955764888 1.08392+0.271753i 1.08392332733869+0.271752585319512i 1.08392332733869454+0.271752585319511717i 11 acosh:0 0 0 1.06128+0.904557i 1.06127506190504+0.904556894302381i 1.06127506190503565+0.904556894302381364i 12 asinh:0.881374 0.881373587019543 0.881373587019543025 1.06128+0.666239i 1.06127506190504+0.666239432492515i 1.06127506190503565+0.666239432492515255i 13 atanh:inf inf inf 0.402359+1.01722i 0.402359478108525+1.01722196789785i 0.402359478108525094+1.01722196789785137i 14 erf:0.842701 0.842700792949715 0.842700792949714869 15 erfc:0.157299 0.157299207050285 0.157299207050285131 16 lgamma:1.79176 1.79175946922805 1.791759469228055 17 lgamma:1.79176 1 1.79175946922805 1 1.791759469228055 1 18 tgamma:6 6 6 -
src/tests/.expect/math3.x64.txt
r8dbedfc r13073be 1 sinh:1.1752 1.1752011936438 1.17520119364380146 0.634964+1.29846i 0.634963914784736+1.29845758141598i 0.634963914784736108+1.29845758141597729i 2 cosh:1.54308 1.54308063481524 1.54308063481524378 0.83373+0.988898i 0.833730025131149+0.988897705762865i 0.833730025131149049+0.988897705762865096i 3 tanh:0.761594 0.761594155955765 0.761594155955764888 1.08392+0.271753i 1.08392332733869+0.271752585319512i 1.08392332733869454+0.271752585319511717i 4 acosh:0 0 0 1.06128+0.904557i 1.06127506190504+0.904556894302381i 1.06127506190503565+0.904556894302381364i 5 asinh:0.881374 0.881373587019543 0.881373587019543025 1.06128+0.666239i 1.06127506190504+0.666239432492515i 1.06127506190503565+0.666239432492515255i 6 atanh:inf inf inf 0.402359+1.01722i 0.402359478108525+1.01722196789785i 0.402359478108525094+1.01722196789785137i 7 erf:0.842701 0.842700792949715 0.842700792949714869 8 erfc:0.157299 0.157299207050285 0.157299207050285131 9 lgamma:1.79176 1.79175946922805 1.791759469228055 10 lgamma:1.79176 1 1.79175946922805 1 1.791759469228055 1 11 tgamma:6 6 6 1 floor:1 1 1 2 ceil:2 2 2 3 trunc:3 3 3 4 rint:2 2 2 5 rint:2 2 2 6 rint:2 2 2 7 lrint:2 2 2 8 llrint:2 2 2 9 nearbyint:4 4 4 10 round:2 2 2 11 round:2 2 2 12 round:2 2 2 13 lround:2 2 2 14 llround:2 2 2 15 copysign:-1 -1 -1 16 frexp:0.5 3 0.5 3 0.5 3 17 ldexp:8 8 8 18 modf:2 0.3 2 0.3 2 0.3 19 modf:2, 0.3 2, 0.3 2, 0.3 20 nextafter:2 2 2 21 nexttoward:2 2 2 22 scalbn:16 16 16 23 scalbln:16 16 16 -
src/tests/.expect/math3.x86.txt
r8dbedfc r13073be 1 sinh:1.1752 1.1752011936438 1.17520119364380146 0.634964+1.29846i 0.634963914784736+1.29845758141598i 0.634963914784736108+1.29845758141597729i 2 cosh:1.54308 1.54308063481524 1.54308063481524378 0.83373+0.988898i 0.833730025131149+0.988897705762865i 0.833730025131149049+0.988897705762865096i 3 tanh:0.761594 0.761594155955765 0.761594155955764888 1.08392+0.271753i 1.08392332733869+0.271752585319512i 1.08392332733869454+0.271752585319511717i 4 acosh:0 0 0 1.06128+0.904557i 1.06127506190504+0.904556894302381i 1.06127506190503565+0.904556894302381364i 5 asinh:0.881374 0.881373587019543 0.881373587019543025 1.06128+0.666239i 1.06127506190504+0.666239432492515i 1.06127506190503565+0.666239432492515255i 6 atanh:inf inf inf 0.402359+1.01722i 0.402359478108525+1.01722196789785i 0.402359478108525094+1.01722196789785137i 7 erf:0.842701 0.842700792949715 0.842700792949714869 8 erfc:0.157299 0.157299207050285 0.157299207050285131 9 lgamma:1.79176 1.79175946922805 1.791759469228055 10 lgamma:1.79176 1 1.79175946922805 1 1.791759469228055 1 11 tgamma:6 6 6 1 floor:1 1 1 2 ceil:2 2 2 3 trunc:3 3 3 4 rint:2 2 2 5 rint:2 2 2 6 rint:2 2 2 7 lrint:2 2 2 8 llrint:2 2 2 9 nearbyint:4 4 4 10 round:2 2 2 11 round:2 2 2 12 round:2 2 2 13 lround:2 2 2 14 llround:2 2 2 15 copysign:-1 -1 -1 16 frexp:0.5 3 0.5 3 0.5 3 17 ldexp:8 8 8 18 modf:2 0.3 2 0.3 2 0.3 19 modf:2, 0.3 2, 0.3 2, 0.3 20 nextafter:2 2 2 21 nexttoward:2 2 2 22 scalbn:16 16 16 23 scalbln:16 16 16 -
src/tests/concurrent/coroutineYield.c
r8dbedfc r13073be 3 3 #include <stdlib> 4 4 #include <thread> 5 #include <time>6 7 #ifndef PREEMPTION_RATE8 #define PREEMPTION_RATE 10`ms9 #endif10 11 Duration default_preemption() {12 return PREEMPTION_RATE;13 }14 5 15 6 #ifdef LONG_TEST -
src/tests/concurrent/examples/matrixSum.c
r8dbedfc r13073be 11 11 // Created On : Mon Oct 9 08:29:28 2017 12 12 // Last Modified By : Peter A. Buhr 13 // Last Modified On : Fri May 25 09:34:27 201814 // Update Count : 1013 // Last Modified On : Tue Dec 5 22:56:46 2017 14 // Update Count : 4 15 15 // 16 16 … … 20 20 21 21 thread Adder { 22 int * row, cols, &subtotal; // communication22 int * row, cols, * subtotal; // communication 23 23 }; 24 24 25 25 void ?{}( Adder & adder, int row[], int cols, int & subtotal ) { 26 adder.[ row, cols ] = [ row, cols ]; // expression disallowed in multi-member access 27 &adder.subtotal = &subtotal; 26 adder.row = row; 27 adder.cols = cols; 28 adder.subtotal = &subtotal; 28 29 } 29 30 30 void main( Adder & adder ) with( adder ) { // thread starts here31 subtotal = 0;32 for ( int c = 0; c < cols; c += 1 ) {33 subtotal += row[c];34 } // for31 void main( Adder & adder ) with( adder ) { 32 *subtotal = 0; 33 for ( int c = 0; c < cols; c += 1 ) { 34 *subtotal += row[c]; 35 } // for 35 36 } 36 37 37 38 int main() { 38 const int rows = 10, cols = 1000;39 int matrix[rows][cols], subtotals[rows], total = 0;40 processor p; // addkernel thread39 const int rows = 10, cols = 1000; 40 int matrix[rows][cols], subtotals[rows], total = 0; 41 processor p; // extra kernel thread 41 42 42 for ( int r = 0; r < rows; r += 1 ) {43 for ( int r = 0; r < rows; r += 1 ) { 43 44 for ( int c = 0; c < cols; c += 1 ) { 44 45 matrix[r][c] = 1; 45 46 } // for 46 } // for47 Adder * adders[rows];48 for ( int r = 0; r < rows; r += 1 ) { // start threads to sum rows47 } // for 48 Adder * adders[rows]; 49 for ( int r = 0; r < rows; r += 1 ) { // start threads to sum rows 49 50 adders[r] = &(*malloc()){ matrix[r], cols, subtotals[r] }; 50 51 // adders[r] = new( matrix[r], cols, &subtotals[r] ); 51 } // for52 for ( int r = 0; r < rows; r += 1 ) { // wait for threads to finish52 } // for 53 for ( int r = 0; r < rows; r += 1 ) { // wait for threads to finish 53 54 delete( adders[r] ); 54 55 total += subtotals[r]; // total subtotals 55 } // for56 sout | total | endl;56 } // for 57 sout | total | endl; 57 58 } 58 59 -
src/tests/concurrent/signal/block.c
r8dbedfc r13073be 14 14 #include <time> 15 15 16 #ifdef LONG_TEST 17 static const unsigned long N = 150_000ul; 18 #else 19 static const unsigned long N = 5_000ul; 20 #endif 21 16 22 #ifndef PREEMPTION_RATE 17 23 #define PREEMPTION_RATE 10`ms … … 21 27 return PREEMPTION_RATE; 22 28 } 23 24 #ifdef LONG_TEST25 static const unsigned long N = 150_000ul;26 #else27 static const unsigned long N = 5_000ul;28 #endif29 29 30 30 enum state_t { WAITED, SIGNAL, BARGE }; -
src/tests/concurrent/signal/disjoint.c
r8dbedfc r13073be 4 4 #include <thread> 5 5 #include <time> 6 7 #ifdef LONG_TEST 8 static const unsigned long N = 300_000ul; 9 #else 10 static const unsigned long N = 10_000ul; 11 #endif 6 12 7 13 #ifndef PREEMPTION_RATE … … 12 18 return PREEMPTION_RATE; 13 19 } 14 15 #ifdef LONG_TEST16 static const unsigned long N = 300_000ul;17 #else18 static const unsigned long N = 10_000ul;19 #endif20 20 21 21 enum state_t { WAIT, SIGNAL, BARGE }; -
src/tests/concurrent/signal/wait.c
r8dbedfc r13073be 12 12 #include <time> 13 13 14 #ifdef LONG_TEST 15 static const unsigned long N = 375_000ul; 16 #else 17 static const unsigned long N = 2_500ul; 18 #endif 19 14 20 #ifndef PREEMPTION_RATE 15 21 #define PREEMPTION_RATE 10`ms … … 19 25 return PREEMPTION_RATE; 20 26 } 21 22 #ifdef LONG_TEST23 static const unsigned long N = 375_000ul;24 #else25 static const unsigned long N = 2_500ul;26 #endif27 27 28 28 monitor global_t {}; -
src/tests/math1.c
r8dbedfc r13073be 10 10 // Created On : Fri Apr 22 14:59:21 2016 11 11 // Last Modified By : Peter A. Buhr 12 // Last Modified On : Thu May 24 21:01:15 201813 // Update Count : 8 512 // Last Modified On : Fri Aug 11 15:16:41 2017 13 // Update Count : 84 14 14 // 15 15 … … 48 48 sout | "\\" | b | b \ e | endl; 49 49 sout | "\\" | 'a' \ 3u | 2 \ 8u | 4 \ 3u | -4 \ 3u | 4 \ -3 | -4 \ -3 | 4.0 \ 2.1 | (1.0f+2.0fi) \ (3.0f+2.0fi) | endl; 50 51 //---------------------- Logarithm ---------------------- 52 53 sout | "log:" | log( 1.0F ) | log( 1.0D ) | log( 1.0L ) | log( 1.0F+1.0FI ) | log( 1.0D+1.0DI ) | log( 1.0DL+1.0LI ) | endl; 54 sout | "log2:" | log2( 8.0F ) | log2( 8.0D ) | log2( 8.0L ) | endl; 55 sout | "log10:" | log10( 100.0F ) | log10( 100.0D ) | log10( 100.0L ) | endl; 56 sout | "log1p:" | log1p( 1.0F ) | log1p( 1.0D ) | log1p( 1.0L ) | endl; 57 sout | "ilogb:" | ilogb( 1.0F ) | ilogb( 1.0D ) | ilogb( 1.0L ) | endl; 58 sout | "logb:" | logb( 8.0F ) | logb( 8.0D ) | logb( 8.0L ) | endl; 59 60 sout | "sqrt:" | sqrt( 1.0F ) | sqrt( 1.0D ) | sqrt( 1.0L ) | sqrt( 1.0F+1.0FI ) | sqrt( 1.0D+1.0DI ) | sqrt( 1.0DL+1.0LI ) | endl; 61 sout | "cbrt:" | cbrt( 27.0F ) | cbrt( 27.0D ) | cbrt( 27.0L ) | endl; 62 sout | "hypot:" | hypot( 1.0F, -1.0F ) | hypot( 1.0D, -1.0D ) | hypot( 1.0L, -1.0L ) | endl; 50 63 } // main 51 64 -
src/tests/math2.c
r8dbedfc r13073be 10 10 // Created On : Fri Apr 22 14:59:21 2016 11 11 // Last Modified By : Peter A. Buhr 12 // Last Modified On : Thu May 24 21:06:10 201813 // Update Count : 8 212 // Last Modified On : Fri Aug 11 15:40:04 2017 13 // Update Count : 81 14 14 // 15 15 … … 21 21 double d; 22 22 long double l; 23 24 //---------------------- Logarithm ----------------------25 26 sout | "log:" | log( 1.0F ) | log( 1.0D ) | log( 1.0L ) | log( 1.0F+1.0FI ) | log( 1.0D+1.0DI ) | log( 1.0DL+1.0LI ) | endl;27 sout | "log2:" | log2( 8.0F ) | log2( 8.0D ) | log2( 8.0L ) | endl;28 sout | "log10:" | log10( 100.0F ) | log10( 100.0D ) | log10( 100.0L ) | endl;29 sout | "log1p:" | log1p( 1.0F ) | log1p( 1.0D ) | log1p( 1.0L ) | endl;30 sout | "ilogb:" | ilogb( 1.0F ) | ilogb( 1.0D ) | ilogb( 1.0L ) | endl;31 sout | "logb:" | logb( 8.0F ) | logb( 8.0D ) | logb( 8.0L ) | endl;32 33 sout | "sqrt:" | sqrt( 1.0F ) | sqrt( 1.0D ) | sqrt( 1.0L ) | sqrt( 1.0F+1.0FI ) | sqrt( 1.0D+1.0DI ) | sqrt( 1.0DL+1.0LI ) | endl;34 sout | "cbrt:" | cbrt( 27.0F ) | cbrt( 27.0D ) | cbrt( 27.0L ) | endl;35 sout | "hypot:" | hypot( 1.0F, -1.0F ) | hypot( 1.0D, -1.0D ) | hypot( 1.0L, -1.0L ) | endl;36 23 37 24 //---------------------- Trigonometric ---------------------- … … 45 32 sout | "atan2:" | atan2( 1.0F, 1.0F ) | atan2( 1.0D, 1.0D ) | atan2( 1.0L, 1.0L ); 46 33 sout | "atan:" | atan( 1.0F, 1.0F ) | atan( 1.0D, 1.0D ) | atan( 1.0L, 1.0L ) | endl; 34 35 //---------------------- Hyperbolic ---------------------- 36 37 sout | "sinh:" | sinh( 1.0F ) | sinh( 1.0D ) | sinh( 1.0L ) | sinh( 1.0F+1.0FI ) | sinh( 1.0D+1.0DI ) | sinh( 1.0DL+1.0LI ) | endl; 38 sout | "cosh:" | cosh( 1.0F ) | cosh( 1.0D ) | cosh( 1.0L ) | cosh( 1.0F+1.0FI ) | cosh( 1.0D+1.0DI ) | cosh( 1.0DL+1.0LI ) | endl; 39 sout | "tanh:" | tanh( 1.0F ) | tanh( 1.0D ) | tanh( 1.0L ) | tanh( 1.0F+1.0FI ) | tanh( 1.0D+1.0DI ) | tanh( 1.0DL+1.0LI ) | endl; 40 sout | "acosh:" | acosh( 1.0F ) | acosh( 1.0D ) | acosh( 1.0L ) | acosh( 1.0F+1.0FI ) | acosh( 1.0D+1.0DI ) | acosh( 1.0DL+1.0LI ) | endl; 41 sout | "asinh:" | asinh( 1.0F ) | asinh( 1.0D ) | asinh( 1.0L ) | asinh( 1.0F+1.0FI ) | asinh( 1.0D+1.0DI ) | asinh( 1.0DL+1.0LI ) | endl; 42 sout | "atanh:" | atanh( 1.0F ) | atanh( 1.0D ) | atanh( 1.0L ) | atanh( 1.0F+1.0FI ) | atanh( 1.0D+1.0DI ) | atanh( 1.0DL+1.0LI ) | endl; 43 44 //---------------------- Error / Gamma ---------------------- 45 46 sout | "erf:" | erf( 1.0F ) | erf( 1.0D ) | erf( 1.0L ) | endl; 47 sout | "erfc:" | erfc( 1.0F ) | erfc( 1.0D ) | erfc( 1.0L ) | endl; 48 sout | "lgamma:" | lgamma( 4.0F ) | lgamma( 4.0D ) | lgamma( 4.0L ) | endl; 49 int sign; 50 f = lgamma( 4.0F, &sign ); 51 sout | "lgamma:" | f | sign; 52 d = lgamma( 4.0D, &sign ); 53 sout | d | sign; 54 l = lgamma( 4.0L, &sign ); 55 sout | l | sign | endl; 56 sout | "tgamma:" | tgamma( 4.0F ) | tgamma( 4.0D ) | tgamma( 4.0L ) | endl; 47 57 } // main 48 58 -
src/tests/math3.c
r8dbedfc r13073be 10 10 // Created On : Fri Apr 22 14:59:21 2016 11 11 // Last Modified By : Peter A. Buhr 12 // Last Modified On : Thu May 24 21:06:12 201813 // Update Count : 8 212 // Last Modified On : Fri Aug 11 15:40:03 2017 13 // Update Count : 81 14 14 // 15 15 … … 22 22 long double l; 23 23 24 //---------------------- Hyperbolic----------------------24 //---------------------- Nearest Integer ---------------------- 25 25 26 sout | "sinh:" | sinh( 1.0F ) | sinh( 1.0D ) | sinh( 1.0L ) | sinh( 1.0F+1.0FI ) | sinh( 1.0D+1.0DI ) | sinh( 1.0DL+1.0LI ) | endl; 27 sout | "cosh:" | cosh( 1.0F ) | cosh( 1.0D ) | cosh( 1.0L ) | cosh( 1.0F+1.0FI ) | cosh( 1.0D+1.0DI ) | cosh( 1.0DL+1.0LI ) | endl; 28 sout | "tanh:" | tanh( 1.0F ) | tanh( 1.0D ) | tanh( 1.0L ) | tanh( 1.0F+1.0FI ) | tanh( 1.0D+1.0DI ) | tanh( 1.0DL+1.0LI ) | endl; 29 sout | "acosh:" | acosh( 1.0F ) | acosh( 1.0D ) | acosh( 1.0L ) | acosh( 1.0F+1.0FI ) | acosh( 1.0D+1.0DI ) | acosh( 1.0DL+1.0LI ) | endl; 30 sout | "asinh:" | asinh( 1.0F ) | asinh( 1.0D ) | asinh( 1.0L ) | asinh( 1.0F+1.0FI ) | asinh( 1.0D+1.0DI ) | asinh( 1.0DL+1.0LI ) | endl; 31 sout | "atanh:" | atanh( 1.0F ) | atanh( 1.0D ) | atanh( 1.0L ) | atanh( 1.0F+1.0FI ) | atanh( 1.0D+1.0DI ) | atanh( 1.0DL+1.0LI ) | endl; 26 sout | "floor:" | floor( 1.2F ) | floor( 1.2D ) | floor( 1.2L ) | endl; 27 sout | "ceil:" | ceil( 1.6F ) | ceil( 1.6D ) | ceil( 1.6L ) | endl; 28 sout | "trunc:" | trunc( 3.5F ) | trunc( 3.5D ) | trunc( 3.5L ) | endl; 29 sout | "rint:" | (float)rint( 1.5F ) | (double)rint( 1.5D ) | (long double)rint( 1.5L ) | endl; 30 sout | "rint:" | (long int)rint( 1.5F ) | (long int)rint( 1.5D ) | (long int)rint( 1.5L ) | endl; 31 sout | "rint:" | (long long int)rint( 1.5F ) | (long long int)rint( 1.5D ) | (long long int)rint( 1.5L ) | endl; 32 sout | "lrint:" | lrint( 1.5F ) | lrint( 1.5D ) | lrint( 1.5L ) | endl; 33 sout | "llrint:" | llrint( 1.5F ) | llrint( 1.5D ) | llrint( 1.5L ) | endl; 34 sout | "nearbyint:" | nearbyint( 3.5F ) | nearbyint( 3.5D ) | nearbyint( 3.5L ) | endl; 35 sout | "round:" | (float)round( 1.5F ) | (double)round( 1.5D ) | (long double)round( 1.5L ) | endl; 36 sout | "round:" | (long int)round( 1.5F ) | (long int)round( 1.5D ) | (long int)round( 1.5L ) | endl; 37 sout | "round:" | (long long int)round( 1.5F ) | (long long int)round( 1.5D ) | (long long int)round( 1.5L ) | endl; 38 sout | "lround:" | lround( 1.5F ) | lround( 1.5D ) | lround( 1.5L ) | endl; 39 sout | "llround:" | llround( 1.5F ) | llround( 1.5D ) | llround( 1.5L ) | endl; 32 40 33 //---------------------- Error / Gamma----------------------41 //---------------------- Manipulation ---------------------- 34 42 35 sout | "erf:" | erf( 1.0F ) | erf( 1.0D ) | erf( 1.0L ) | endl; 36 sout | "erfc:" | erfc( 1.0F ) | erfc( 1.0D ) | erfc( 1.0L ) | endl; 37 sout | "lgamma:" | lgamma( 4.0F ) | lgamma( 4.0D ) | lgamma( 4.0L ) | endl; 38 int sign; 39 f = lgamma( 4.0F, &sign ); 40 sout | "lgamma:" | f | sign; 41 d = lgamma( 4.0D, &sign ); 42 sout | d | sign; 43 l = lgamma( 4.0L, &sign ); 44 sout | l | sign | endl; 45 sout | "tgamma:" | tgamma( 4.0F ) | tgamma( 4.0D ) | tgamma( 4.0L ) | endl; 43 sout | "copysign:" | copysign( 1.0F, -1.0F ) | copysign( 1.0D, -1.0D ) | copysign( 1.0L, -1.0L ) | endl; 44 int exp; 45 f = frexp( 4.0F, &exp ); 46 sout | "frexp:" | f | exp; 47 d = frexp( 4.0D, &exp ); 48 sout | d | exp; 49 l = frexp( 4.0L, &exp ); 50 sout | l | exp | endl; 51 sout | "ldexp:" | ldexp( 2.0F, 2 ) | ldexp( 2.0D, 2 ) | ldexp( 2.0L, 2 ) | endl; 52 float fi; 53 double di; 54 long double ldi; 55 f = modf( 2.3F, &fi ); 56 sout | "modf:" | fi | f; 57 d = modf( 2.3D, &di ); 58 sout | di | d; 59 l = modf( 2.3L, &ldi ); 60 sout | ldi | l | endl; 61 sout | "modf:" | modf( 2.3F ) | modf( 2.3D ) | modf( 2.3L ) | endl; 62 sout | "nextafter:" | nextafter( 2.0F, 3.0F ) | nextafter( 2.0D, 3.0D ) | nextafter( 2.0L, 3.0L ) | endl; 63 sout | "nexttoward:" | nexttoward( 2.0F, 3.0F ) | nexttoward( 2.0D, 3.0D ) | nexttoward( 2.0L, 3.0L ) | endl; 64 65 sout | "scalbn:" | scalbn( 2.0F, 3 ) | scalbn( 2.0D, 3 ) | scalbn( 2.0L, 3 ) | endl; 66 sout | "scalbln:" | scalbln( 2.0F, 3L ) | scalbln( 2.0D, 3L ) | scalbln( 2.0L, 3L ) | endl; 46 67 } // main 47 68 -
src/tests/preempt_longrun/Makefile.am
r8dbedfc r13073be 17 17 repeats=10 18 18 max_time=600 19 preempt=1 0ul\`ms19 preempt=1_000ul 20 20 debug=-debug 21 21 -
src/tests/preempt_longrun/Makefile.in
r8dbedfc r13073be 450 450 repeats = 10 451 451 max_time = 600 452 preempt = 1 0ul\`ms452 preempt = 1_000ul 453 453 debug = -debug 454 454 REPEAT = ${abs_top_srcdir}/tools/repeat -
src/tests/preempt_longrun/create.c
r8dbedfc r13073be 1 1 #include <kernel> 2 2 #include <thread> 3 #include <time> 3 4 static const unsigned long N = 60_000ul; 4 5 5 6 #ifndef PREEMPTION_RATE 6 # error PREEMPTION_RATE not defined in makefile7 #define PREEMPTION_RATE 10`ms 7 8 #endif 8 9 … … 10 11 return PREEMPTION_RATE; 11 12 } 12 13 static const unsigned long N = 60_000ul;14 13 15 14 thread worker_t {}; -
src/tests/preempt_longrun/enter.c
r8dbedfc r13073be 2 2 #include <monitor> 3 3 #include <thread> 4 #include <time> 4 5 static const unsigned long N = 2_100_000ul; 5 6 6 7 #ifndef PREEMPTION_RATE 7 # error PREEMPTION_RATE not defined in makefile8 #define PREEMPTION_RATE 10`ms 8 9 #endif 9 10 … … 11 12 return PREEMPTION_RATE; 12 13 } 13 14 static const unsigned long N = 2_100_000ul;15 14 16 15 monitor mon_t {}; -
src/tests/preempt_longrun/enter3.c
r8dbedfc r13073be 2 2 #include <monitor> 3 3 #include <thread> 4 #include <time> 4 5 static const unsigned long N = 500_000ul; 5 6 6 7 #ifndef PREEMPTION_RATE 7 # error PREEMPTION_RATE not defined in makefile8 #define PREEMPTION_RATE 10`ms 8 9 #endif 9 10 … … 11 12 return PREEMPTION_RATE; 12 13 } 13 14 static const unsigned long N = 500_000ul;15 14 16 15 monitor mon_t {}; -
src/tests/preempt_longrun/processor.c
r8dbedfc r13073be 1 1 #include <kernel> 2 2 #include <thread> 3 #include <time> 3 4 static const unsigned long N = 5_000ul; 4 5 5 6 #ifndef PREEMPTION_RATE 6 # error PREEMPTION_RATE not defined in makefile7 #define PREEMPTION_RATE 10`ms 7 8 #endif 8 9 … … 10 11 return PREEMPTION_RATE; 11 12 } 12 13 static const unsigned long N = 5_000ul;14 13 15 14 int main(int argc, char* argv[]) { -
src/tests/preempt_longrun/stack.c
r8dbedfc r13073be 1 1 #include <kernel> 2 #include <thread> 3 2 4 #include <math> 3 #include <thread>4 #include <time>5 5 6 6 #ifndef PREEMPTION_RATE 7 # error PREEMPTION_RATE not defined in makefile7 #define PREEMPTION_RATE 10`ms 8 8 #endif 9 9 -
src/tests/preempt_longrun/yield.c
r8dbedfc r13073be 1 1 #include <kernel> 2 2 #include <thread> 3 #include <time>4 5 #ifndef PREEMPTION_RATE6 #error PREEMPTION_RATE not defined in makefile7 #endif8 9 Duration default_preemption() {10 return PREEMPTION_RATE;11 }12 3 13 4 #ifdef LONG_TEST … … 16 7 static const unsigned long N = 325_000ul; 17 8 #endif 9 10 #ifndef PREEMPTION_RATE 11 #define PREEMPTION_RATE 10`ms 12 #endif 13 14 Duration default_preemption() { 15 return PREEMPTION_RATE; 16 } 18 17 19 18 thread worker_t {}; -
src/tests/test.py
r8dbedfc r13073be 78 78 else : 79 79 print('ERROR: No expected file for test %s, ignoring it' % testname, file=sys.stderr) 80 81 # make sure we have at least some test to run 82 if not tests : 83 print('ERROR: No valid test to run', file=sys.stderr) 84 sys.exit(1) 80 85 81 86 return tests … … 261 266 tests = validTests( options ) 262 267 263 # make sure we have at least some test to run264 if not tests :265 print('ERROR: No valid test to run', file=sys.stderr)266 sys.exit(1)267 268 269 268 # sort the test alphabetically for convenience 270 269 tests.sort(key=lambda t: (t.arch if t.arch else '') + t.target())
Note:
See TracChangeset
for help on using the changeset viewer.