DOCSLIB.ORG

Computer Science & Engineering 150A Problem Solving Using

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

CSCE150A Computer Science & Engineering 150A Introduction Problem Solving Using Computers Language Elements General Form Lecture 02 - Introduction To C Operators & Expressions Formatting I/O Stephen Scott Running Programs (Adapted from Christopher M. Bourke) Common Pitfalls Fall 2009 1 / 77 [email protected] CSCE150A Introduction C Language Elements Language Variable Declarations and Data Types Elements General Form Executable Statements Operators & General Form of a C Program Expressions Formatting Arithmetic Expressions I/O Running Formatting Numbers in Program Output Programs Interactive Mode, Batch Mode, and Data Files Common Pitfalls Common Programming Errors 2 / 77 Overview of C Programming CSCE150A Introduction Language Elements This chapter introduces C { a high-level programming language developed General Form in 1972 by Dennis Ritchie at AT&T Bell Laboratories. Operators & Expressions This chapter describes the elements of a C program and the types of data Formatting I/O that can be processed by C. It also describes C statements for performing Running computations, for entering data, and for displaying results. Programs Common Pitfalls 3 / 77 C Language Elements CSCE150A Introduction Preprocessor Directives Language Elements Syntax Displays for Preprocessor Directives Preprocessor Comments \int main()" Function Main Function Reserved Words Reserved Words Program Style Executable Statements Standard Identifiers Input/Output General Form User-Defined Identifiers Operators & Uppercase and Lowercase Letters Expressions Formatting Program Style I/O Running Programs Common 4 / 77 Pitfalls Preprocessor Directives CSCE150A Introduction Language The C preprocessor modifies the text of the C program before it is Elements passed to the compiler. Preprocessor Comments Main Function Preprocessor directives are C program lines beginning with a # that Reserved Words Program Style provide instructions to the C preprocessor. Executable Statements Input/Output Preprocessor directives begins with a #, e.g. #include and #define. General Form Predefined libraries are useful functions and symbols that are Operators & Expressions predefined by the C language (standard libraries). Formatting I/O Running Programs Common 5 / 77 Pitfalls #include and #define CSCE150A Introduction #include<libraryName> gives the program access to a library Language Elements Example: #include<stdio.h> (standard input and output) has Preprocessor Comments definitions for input and output, such as printf and scanf. Main Function Reserved Words #define NAME value associates a constant macro Program Style Executable Statements Example: Input/Output General Form 1 #defineKMS_PER_MILE 1.609 Operators & 2 #definePI 3.14159 Expressions Formatting I/O Running Programs Common 6 / 77 Pitfalls Comments CSCE150A Introduction Comments provide supplementary information making it easier for us to Language Elements understand the program, but comments are ignored by the C preprocessor Preprocessor Comments and compiler. Main Function Reserved Words Program Style - anything between them with be considered a comment, even Executable /**/ Statements Input/Output if they span multiple lines. General Form // - anything after this and before the end of the line is considered a Operators & Expressions comment. Formatting I/O Running Programs Common 7 / 77 Pitfalls Function main CSCE150A The point at which a C program begins execution is the main Introduction Language function: Elements Preprocessor 1 int main(void) Comments Main Function Reserved Words Program Style Every C program must have a main function. Executable Statements Input/Output The main function (and every other function) body has two parts: General Form Declarations - tell the compiler what memory cells are needed in the Operators & function Expressions Executable statements - (derived from the algorithm) are translated Formatting I/O into machine language and later executed Running Programs Common 8 / 77 Pitfalls Function main CSCE150A Introduction Language Elements All C functions contain punctuation and special symbols Preprocessor Comments Punctuation - commas separate items in a list, semicolons appear at Main Function Reserved Words the end of each statement Program Style Executable Special symbols: *, =, {, }, etc. Statements Input/Output Curly braces mark the beginning and end of the body of every General Form function, including main Operators & Expressions Formatting I/O Running Programs Common 9 / 77 Pitfalls Reserved Words CSCE150A Introduction A word that has special meaning in C. E.g.: Language int - Indicates that the main function (or any other function) returns Elements Preprocessor an integer value, or that a memory cell will store an integer value Comments - Indicates that a function returns a real number or that a Main Function double Reserved Words memory cell will store a real number Program Style Executable Statements Always lower case Input/Output General Form Can not be used for other purposes Operators & Appendix E has a full listing of reserved words (ex: Expressions Formatting double, int, if, else, void, return etc.) I/O Running Programs Common 10 / 77 Pitfalls Standard Identifiers CSCE150A Introduction Language Standard identifiers have a special meaning in C (assigned by Elements Preprocessor standard libraries). Comments Main Function Standard identifiers can be redefined and used by the programmer for Reserved Words Program Style other purposes Executable Statements Not recommended If you redefine a standard identifier; C will no Input/Output longer be able to use it for its original purpose. General Form Operators & Examples: input/output functions printf, scanf Expressions Formatting I/O Running Programs Common 11 / 77 Pitfalls User-Defined Identifiers CSCE150A We choose our own identifiers to name memory cells that will hold data Introduction and program results and to name operations (functions) that we define Language Elements (more on this in Chapter 3) Preprocessor Comments Main Function An identifier must consist only of letters , digits , Reserved Words [a-zA-Z] [0-9] Program Style Executable and underscores. Statements Input/Output An identifier cannot begin with a digit (and shouldn't begin with an General Form underscore). Operators & Expressions A C reserved word cannot be used as an identifier. Formatting I/O An identifier defined in a C standard library should not be redefined. Running Programs Common 12 / 77 Pitfalls User-Defined Identifiers CSCE150A Examples: letter_1, Inches, KMS_PER_MILE Introduction Some compilers will only see the first 31 characters Language Elements Uppercase and lowercase are different Preprocessor Comments (Variable, variable, VARIABLE are all different) Main Function Reserved Words Choosing identifer names: Program Style Executable Statements Choose names that mean something Input/Output Should be easy to read and understand General Form Shorten only if possible Operators & Expressions Don't use Big, big, and BIG as they are easy to confuse Formatting I/O Identifiers using all-caps are usually used for preprocessor-defined Running constants (#define) Programs Common 13 / 77 Pitfalls Program Style CSCE150A Introduction Language Elements Preprocessor A program that \looks good" is easier to read and understand than one Comments Main Function that is sloppy (i.e. good spacing, well-named identifiers). Reserved Words Program Style Executable In industry, programmers spend considerably more time on program Statements Input/Output maintenance than they do on its original design or coding. General Form Operators & Expressions Formatting I/O Running Programs Common 14 / 77 Pitfalls Style Tips Rigorous Comments CSCE150A Introduction Language The number of comments in your program doesn't affect its speed or Elements size. Preprocessor Comments Main Function Always best to include as much documentation as possible in the Reserved Words Program Style form of comments. Executable Statements Input/Output Begin each program or function with a full explanation of its inputs, General Form outputs, and how it works. Operators & Expressions Include comments as necessary throughout the program Formatting I/O Running Programs Common 15 / 77 Pitfalls Style Tips Naming Conventions CSCE150A Introduction Language Give your variables meaningful names (identifiers) Elements Preprocessor Comments x,y may be good if you're dealing with coordinates, but bad in Main Function Reserved Words general. Program Style Executable myVariable, aVariable, anInteger, etc are bad: they do not Statements Input/Output describe the purpose of the variable. General Form tempInt,PI, numberOfStudents are good because they do. Operators & Expressions Formatting I/O Running Programs Common 16 / 77 Pitfalls Style Tips CamelCaseNotation CSCE150A Old School C convention: separate compound words with underscores Introduction Language number_of_students, interest_rate, max_value, etc. Elements Preprocessor Underscore (shift-hyphen) is inconvenient Comments Main Function Solution: camelCaseNotation - connect compound words with Reserved Words Program Style upper-case letters. Executable Statements Input/Output Example: numberOfStudents, interestRate, maxValue, etc. General Form Much easier to shift-capitalize Operators & Expressions Much more readable Formatting I/O Ubiquitous outside of programming: MasterCard, PetsMart, etc. Running Programs Common 17 / 77 Pitfalls Preprocessor Directives Reserved Words Variables Special Symbols Punctuation Anatomy of a Program CSCE150A 1 /* 2 * Converts distances from miles to kilometers.
Recommended publications
  • PRE PROCESSOR DIRECTIVES in –C LANGUAGE. 2401 – Course

    PRE PROCESSOR DIRECTIVES in –C LANGUAGE. 2401 – Course

    PRE PROCESSOR DIRECTIVES IN –C LANGUAGE. 2401 – Course Notes. 1 The C preprocessor is a macro processor that is used automatically by the C compiler to transform programmer defined programs before actual compilation takes place. It is called a macro processor because it allows the user to define macros, which are short abbreviations for longer constructs. This functionality allows for some very useful and practical tools to design our programs. To include header files(Header files are files with pre defined function definitions, user defined data types, declarations that can be included.) To include macro expansions. We can take random fragments of C code and abbreviate them into smaller definitions namely macros, and once they are defined and included via header files or directly onto the program itself it(the user defined definition) can be used everywhere in the program. In other words it works like a blank tile in the game scrabble, where if one player possesses a blank tile and uses it to state a particular letter for a given word he chose to play then that blank piece is used as that letter throughout the game. It is pretty similar to that rule. Special pre processing directives can be used to, include or exclude parts of the program according to various conditions. To sum up, preprocessing directives occurs before program compilation. So, it can be also be referred to as pre compiled fragments of code. Some possible actions are the inclusions of other files in the file being compiled, definitions of symbolic constants and macros and conditional compilation of program code and conditional execution of preprocessor directives.
  • C and C++ Preprocessor Directives #Include #Define Macros Inline

    C and C++ Preprocessor Directives #Include #Define Macros Inline

    MODULE 10 PREPROCESSOR DIRECTIVES My Training Period: hours Abilities ▪ Able to understand and use #include. ▪ Able to understand and use #define. ▪ Able to understand and use macros and inline functions. ▪ Able to understand and use the conditional compilation – #if, #endif, #ifdef, #else, #ifndef and #undef. ▪ Able to understand and use #error, #pragma, # and ## operators and #line. ▪ Able to display error messages during conditional compilation. ▪ Able to understand and use assertions. 10.1 Introduction - For C/C++ preprocessor, preprocessing occurs before a program is compiled. A complete process involved during the preprocessing, compiling and linking can be read in Module W. - Some possible actions are: ▪ Inclusion of other files in the file being compiled. ▪ Definition of symbolic constants and macros. ▪ Conditional compilation of program code or code segment. ▪ Conditional execution of preprocessor directives. - All preprocessor directives begin with #, and only white space characters may appear before a preprocessor directive on a line. 10.2 The #include Preprocessor Directive - The #include directive causes copy of a specified file to be included in place of the directive. The two forms of the #include directive are: //searches for header files and replaces this directive //with the entire contents of the header file here #include <header_file> - Or #include "header_file" e.g. #include <stdio.h> #include "myheader.h" - If the file name is enclosed in double quotes, the preprocessor searches in the same directory (local) as the source file being compiled for the file to be included, if not found then looks in the subdirectory associated with standard header files as specified using angle bracket. - This method is normally used to include user or programmer-defined header files.
  • Section “Common Predefined Macros” in the C Preprocessor

    Section “Common Predefined Macros” in the C Preprocessor

    The C Preprocessor For gcc version 12.0.0 (pre-release) (GCC) Richard M. Stallman, Zachary Weinberg Copyright c 1987-2021 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation. A copy of the license is included in the section entitled \GNU Free Documentation License". This manual contains no Invariant Sections. The Front-Cover Texts are (a) (see below), and the Back-Cover Texts are (b) (see below). (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Table of Contents 1 Overview :::::::::::::::::::::::::::::::::::::::: 1 1.1 Character sets:::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Initial processing ::::::::::::::::::::::::::::::::::::::::::::::: 2 1.3 Tokenization ::::::::::::::::::::::::::::::::::::::::::::::::::: 4 1.4 The preprocessing language :::::::::::::::::::::::::::::::::::: 6 2 Header Files::::::::::::::::::::::::::::::::::::: 7 2.1 Include Syntax ::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.2 Include Operation :::::::::::::::::::::::::::::::::::::::::::::: 8 2.3 Search Path :::::::::::::::::::::::::::::::::::::::::::::::::::: 9 2.4 Once-Only Headers::::::::::::::::::::::::::::::::::::::::::::: 9 2.5 Alternatives to Wrapper #ifndef ::::::::::::::::::::::::::::::
  • GPU Directives

    GPU Directives

    OPENACC® DIRECTIVES FOR ACCELERATORS NVIDIA GPUs Reaching Broader Set of Developers 1,000,000’s CAE CFD Finance Rendering Universities Data Analytics Supercomputing Centers Life Sciences 100,000’s Oil & Gas Defense Weather Research Climate Early Adopters Plasma Physics 2004 Present Time 2 3 Ways to Accelerate Applications with GPUs Applications Programming Libraries Directives Languages “Drop-in” Quickly Accelerate Maximum Acceleration Existing Applications Performance 3 Directives: Add A Few Lines of Code OpenMP OpenACC CPU CPU GPU main() { main() { double pi = 0.0; long i; double pi = 0.0; long i; #pragma acc parallel #pragma omp parallel for reduction(+:pi) for (i=0; i<N; i++) for (i=0; i<N; i++) { { double t = (double)((i+0.05)/N); double t = (double)((i+0.05)/N); pi += 4.0/(1.0+t*t); pi += 4.0/(1.0+t*t); } } printf(“pi = %f\n”, pi/N); printf(“pi = %f\n”, pi/N); } } OpenACC: Open Programming Standard for Parallel Computing “ OpenACC will enable programmers to easily develop portable applications that maximize the performance and power efficiency benefits of the hybrid CPU/GPU architecture of Titan. ” Buddy Bland Titan Project Director Easy, Fast, Portable Oak Ridge National Lab “ OpenACC is a technically impressive initiative brought together by members of the OpenMP Working Group on Accelerators, as well as many others. We look forward to releasing a version of this proposal in the next release of OpenMP. ” Michael Wong CEO, OpenMP http://www.openacc-standard.org/ Directives Board OpenACC Compiler directives to specify parallel regions
  • Advanced Perl

    Advanced Perl

    Advanced Perl Boston University Information Services & Technology Course Coordinator: Timothy Kohl Last Modified: 05/12/15 Outline • more on functions • references and anonymous variables • local vs. global variables • packages • modules • objects 1 Functions Functions are defined as follows: sub f{ # do something } and invoked within a script by &f(parameter list) or f(parameter list) parameters passed to a function arrive in the array @_ sub print_sum{ my ($a,$b)=@_; my $sum; $sum=$a+$b; print "The sum is $sum\n"; } And so, in the invocation $a = $_[0] = 2 print_sum(2,3); $b = $_[1] = 3 2 The directive my indicates that the variable is lexically scoped. That is, it is defined only for the duration of the given code block between { and } which is usually the body of the function anyway. * When this is done, one is assured that the variables so defined are local to the given function. We'll discuss the difference between local and global variables later. * with some exceptions which we'll discuss To return a value from a function, you can either use an explicit return statement or simply put the value to be returned as the last line of the function. Typically though, it’s better to use the return statement. Ex: sub sum{ my ($a,$b)=@_; my $sum; $sum=$a+$b; return $sum; } $s=sum(2,3); One can also return an array or associative array from a function. 3 References and Anonymous Variables In languages like C one has the notion of a pointer to a given data type, which can be used later on to read and manipulate the contents of the variable pointed to by the pointer.
  • Perl

    Perl

    -I<directory> directories specified by –I are Perl prepended to @INC -I<oct_name> enable automatic line-end processing Ming- Hwa Wang, Ph.D. -(m|M)[- executes use <module> before COEN 388 Principles of Computer- Aided Engineering Design ]<module>[=arg{,arg}] executing your script Department of Computer Engineering -n causes Perl to assume a loop around Santa Clara University -p your script -P causes your script through the C Scripting Languages preprocessor before compilation interpreter vs. compiler -s enable switch parsing efficiency concerns -S makes Perl use the PATH environment strong typed vs. type-less variable to search for the script Perl: Practical Extraction and Report Language -T forces taint checks to be turned on so pattern matching capability you can test them -u causes Perl to dump core after Resources compiling your script Unix Perl manpages -U allow Perl to do unsafe operations Usenet newsgroups: comp.lang.perl -v print version Perl homepage: http://www.perl/com/perl/, http://www.perl.org -V print Perl configuration and @INC Download: http://www.perl.com/CPAN/ values -V:<name> print the value of the named To Run Perl Script configuration value run as command: perl –e ‘print “Hello, world!\n”;’ -w print warning for unused variable, run as scripts (with chmod +x): perl <script> using variable without setting the #!/usr/local/bin/perl –w value, undefined functions, references use strict; to undefined filehandle, write to print “Hello, world!\n”; filehandle which is read-only, using a exit 0; non-number as it were a number, or switches subroutine recurse too deep, etc.
  • Python Guide Documentation 0.0.1

    Python Guide Documentation 0.0.1

    Python Guide Documentation 0.0.1 Kenneth Reitz 2015 09 13 Contents 1 Getting Started 3 1.1 Picking an Interpreter..........................................3 1.2 Installing Python on Mac OS X.....................................5 1.3 Installing Python on Windows......................................6 1.4 Installing Python on Linux........................................7 2 Writing Great Code 9 2.1 Structuring Your Project.........................................9 2.2 Code Style................................................ 15 2.3 Reading Great Code........................................... 24 2.4 Documentation.............................................. 24 2.5 Testing Your Code............................................ 26 2.6 Common Gotchas............................................ 30 2.7 Choosing a License............................................ 33 3 Scenario Guide 35 3.1 Network Applications.......................................... 35 3.2 Web Applications............................................ 36 3.3 HTML Scraping............................................. 41 3.4 Command Line Applications....................................... 42 3.5 GUI Applications............................................. 43 3.6 Databases................................................. 45 3.7 Networking................................................ 45 3.8 Systems Administration......................................... 46 3.9 Continuous Integration.......................................... 49 3.10 Speed..................................................
  • C Programming Tutorial

    C Programming Tutorial

    C Programming Tutorial C PROGRAMMING TUTORIAL Simply Easy Learning by tutorialspoint.com tutorialspoint.com i COPYRIGHT & DISCLAIMER NOTICE All the content and graphics on this tutorial are the property of tutorialspoint.com. Any content from tutorialspoint.com or this tutorial may not be redistributed or reproduced in any way, shape, or form without the written permission of tutorialspoint.com. Failure to do so is a violation of copyright laws. This tutorial may contain inaccuracies or errors and tutorialspoint provides no guarantee regarding the accuracy of the site or its contents including this tutorial. If you discover that the tutorialspoint.com site or this tutorial content contains some errors, please contact us at [email protected] ii Table of Contents C Language Overview .............................................................. 1 Facts about C ............................................................................................... 1 Why to use C ? ............................................................................................. 2 C Programs .................................................................................................. 2 C Environment Setup ............................................................... 3 Text Editor ................................................................................................... 3 The C Compiler ............................................................................................ 3 Installation on Unix/Linux ............................................................................
  • Assembly Language Programming

    Assembly Language Programming

    Experiment 3 Assembly Language Programming Every computer, no matter how simple or complex, has a microprocessor that manages the computer's arithmetical, logical and control activities. A computer program is a collection of numbers stored in memory in the form of ones and zeros. CPU reads these numbers one at a time, decodes them and perform the required action. We term these numbers as machine language. Although machine language instructions make perfect sense to computer but humans cannot comprehend them. A long time ago, someone came up with the idea that computer programs could be written using words instead of numbers and a new language of mnemonics was de- veloped and named as assembly language. An assembly language is a low-level programming language and there is a very strong (generally one-to-one) correspondence between the language and the architecture's machine code instructions. We know that computer cannot interpret assembly language instructions. A program should be developed that performs the task of translating the assembly language instructions to ma- chine language. A computer program that translates the source code written with mnemonics into the executable machine language instructions is called an assembler. The input of an assembler is a source code and its output is an executable object code. Assembly language programs are not portable because assembly language instructions are specific to a particular computer architecture. Similarly, a different assembler is required to make an object code for each platform. The ARM Architecture The ARM is a Reduced Instruction Set Computer(RISC) with a relatively simple implementation of a load/store architecture, i.e.
  • Introduction to GPU Programming with CUDA and Openacc

    Introduction to GPU Programming with CUDA and Openacc

    Introduction to GPU Programming with CUDA and OpenACC Alabama Supercomputer Center 1 Alabama Research and Education Network Contents Topics § Why GPU chips and CUDA? § GPU chip architecture overview § CUDA programming § Queue system commands § Other GPU programming options § OpenACC programming § Comparing GPUs to other processors 2 What is a GPU chip? GPU § A Graphic Processing Unit (GPU) chips is an adaptation of the technology in a video rendering chip to be used as a math coprocessor. § The earliest graphic cards simply mapped memory bytes to screen pixels – i.e. the Apple ][ in 1980. § The next generation of graphics cards (1990s) had 2D rendering capabilities for rendering lines and shaded areas. § Graphics cards started accelerating 3D rendering with standards like OpenGL and DirectX in the early 2000s. § The most recent graphics cards have programmable processors, so that game physics can be offloaded from the main processor to the GPU. § A series of GPU chips sometimes called GPGPU (General Purpose GPU) have double precision capability so that they can be used as math coprocessors. 3 Why GPUs? GPU Comparison of peak theoretical GFLOPs and memory bandwidth for NVIDIA GPUs and Intel CPUs over the past few years. Graphs from the NVIDIA CUDA C Programming Guide 4.0. 4 CUDA Programming Language CUDA The GPU chips are massive multithreaded, manycore SIMD processors. SIMD stands for Single Instruction Multiple Data. Previously chips were programmed using standard graphics APIs (DirectX, OpenGL). CUDA, an extension of C, is the most popular GPU programming language. CUDA can also be called from a C++ program. The CUDA standard has no FORTRAN support, but Portland Group sells a third party CUDA FORTRAN.
  • CUDA C++ Programming Guide

    CUDA C++ Programming Guide

    CUDA C++ Programming Guide Design Guide PG-02829-001_v11.4 | September 2021 Changes from Version 11.3 ‣ Added Graph Memory Nodes. ‣ Formalized Asynchronous SIMT Programming Model. CUDA C++ Programming Guide PG-02829-001_v11.4 | ii Table of Contents Chapter 1. Introduction........................................................................................................ 1 1.1. The Benefits of Using GPUs.....................................................................................................1 1.2. CUDA®: A General-Purpose Parallel Computing Platform and Programming Model....... 2 1.3. A Scalable Programming Model.............................................................................................. 3 1.4. Document Structure................................................................................................................. 5 Chapter 2. Programming Model.......................................................................................... 7 2.1. Kernels.......................................................................................................................................7 2.2. Thread Hierarchy...................................................................................................................... 8 2.3. Memory Hierarchy...................................................................................................................10 2.4. Heterogeneous Programming................................................................................................11 2.5. Asynchronous
  • Directive-Based Programming with Openmp Shared Memory Programming

    Directive-Based Programming with Openmp Shared Memory Programming

    Directive-Based Programming with OpenMP Shared Memory Programming • Explicit thread creation (pthreads): pthread t thread; pthread create(&thread, &attr, some_function, (void ∗) &result); … pthread join(thread, NULL); • Tasks (C++ 11): auto handle = std::async(std::launch::async, some_code, ...); auto result = handle.get(); • Kernels (CUDA): __global__ void someKernel(...) { int idx = blockIdx.x*blockDim.x + threadIdx.x // execute code for given index } 23 OpenMP • API for shared memory parallel programming targeting Fortran, C and C++ • specifications maintained by OpenMP Architecture Review Board (ARB) • members include AMD, ARM, Cray, Intel, Fujitsu, IBM, NVIDIA – versions 1.0 (Fortran ’97, C ’98) - 3.1 (2011) shared memory – 4.0 (2013) accelerators, NUMA – 4.5 (2015) improved memory mapping, SIMD – 5.0 (2018) improved accelerator support 25 OpenMP • comprises compiler directives, library routines and environment variables – C directives (case sensitive) #pragma omp directive-name [clause-list] – library calls begin with omp void omp_set_num_threads(int nthreads); – environment variables begin with OMP export OMP_NUM_THREADS=4 • requires compiler support – activated via -fopenmp (gcc/clang) or -openmp (icc) compiler flags 26 The parallel Directive • OpenMP uses a fork/join model: programs execute serially until they encounter a parallel directive: – this creates a group of threads – number of threads is dependent on the OMP_NUM_THREADS environment variable or set via function call, e.g. omp_set_num_threads(nthreads) – main thread becomes