Development Tools. Akim D le Roland Levillain June 14, 2012
|
|
|
- Adele Booker
- 6 years ago
- Views:
Transcription
1 Development Tools Akim D le Roland Levillain EPITA École Pour l Informatique et les Techniques Avancées June 14, 2012
2 Development Tools 1 tc Tasks 2 3 A. D le, R. Levillain Development Tools 2 / 40
3 1 tc Tasks 2 3
4 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
5 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
6 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
7 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
8 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
9 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
10 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
11 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
12 The Tiger Compiler layout One module, one namespace One library per module, with a pure interface ( libfoo.* ) One task set per module, maybe impure ( tasks.* ) Tasks describe the command line interface Requirements over tasks order One class, one file base name: foo.hh Interface foo.hxx Inline implementation foo.cc Implementation A. D le, R. Levillain Development Tools 4 / 40
13 Tasks: ast/tasks.hh namespace ast { namespace tasks { /// Global root node of abstract syntax tree. extern ast::decslist* the_program; TASK_GROUP ("2. Abstract Syntax Tree"); /// Display the abstract syntax tree TASK_DECLARE ("A ast-display", "display the AST", ast_display, "parse"); /// Free the ast (if defined) TASK_DECLARE ("D ast-delete", "delete the AST", ast_delete, "parse"); } // namespace tasks } // namespace ast A. D le, R. Levillain Development Tools 5 / 40
14 Tasks: ast/tasks.cc namespace ast { namespace tasks { ast::decslist* the_program = 0; void ast_display () { precondition (the_program); std::cout << "/* Abstract Syntax Tree. */" << std::endl << *the_program << std::endl; } void ast_delete () { delete the_program; the_program = 0; } } // namespace tasks } // namespace ast A. D le, R. Levillain Development Tools 6 / 40
15 1 tc Tasks 2 GNU Tools Autoconf for tc Automake for tc 3
16 GNU Tools 1 tc Tasks 2 GNU Tools Autoconf for tc Automake for tc 3
17 GNU Tools Autoconf for tc Automake for tc GNU Autotools aclocal Create aclocal.m4 from configure.ac s requests autoconf Create configure from configure.ac and aclocal.m4 autoheader Create config.h.in from configure.ac (and aclocal.m4 ) automake Create Makefile.in from Makefile.am and configure.ac autoreconf Run them as needed (autoreconf -fivm) Read Alexandre Duret-Lutz s Tutorial [1] A. D le, R. Levillain Development Tools 9 / 40
18 GNU Tools Autoconf for tc Automake for tc GNU Autotools aclocal Create aclocal.m4 from configure.ac s requests autoconf Create configure from configure.ac and aclocal.m4 autoheader Create config.h.in from configure.ac (and aclocal.m4 ) automake Create Makefile.in from Makefile.am and configure.ac autoreconf Run them as needed (autoreconf -fivm) Read Alexandre Duret-Lutz s Tutorial [1] A. D le, R. Levillain Development Tools 9 / 40
19 GNU Tools Autoconf for tc Automake for tc GNU Autotools aclocal Create aclocal.m4 from configure.ac s requests autoconf Create configure from configure.ac and aclocal.m4 autoheader Create config.h.in from configure.ac (and aclocal.m4 ) automake Create Makefile.in from Makefile.am and configure.ac autoreconf Run them as needed (autoreconf -fivm) Read Alexandre Duret-Lutz s Tutorial [1] A. D le, R. Levillain Development Tools 9 / 40
20 GNU Tools Autoconf for tc Automake for tc GNU Autotools aclocal Create aclocal.m4 from configure.ac s requests autoconf Create configure from configure.ac and aclocal.m4 autoheader Create config.h.in from configure.ac (and aclocal.m4 ) automake Create Makefile.in from Makefile.am and configure.ac autoreconf Run them as needed (autoreconf -fivm) Read Alexandre Duret-Lutz s Tutorial [1] A. D le, R. Levillain Development Tools 9 / 40
21 GNU Tools Autoconf for tc Automake for tc GNU Autotools aclocal Create aclocal.m4 from configure.ac s requests autoconf Create configure from configure.ac and aclocal.m4 autoheader Create config.h.in from configure.ac (and aclocal.m4 ) automake Create Makefile.in from Makefile.am and configure.ac autoreconf Run them as needed (autoreconf -fivm) Read Alexandre Duret-Lutz s Tutorial [1] A. D le, R. Levillain Development Tools 9 / 40
22 GNU Tools Autoconf for tc Automake for tc GNU Autotools aclocal Create aclocal.m4 from configure.ac s requests autoconf Create configure from configure.ac and aclocal.m4 autoheader Create config.h.in from configure.ac (and aclocal.m4 ) automake Create Makefile.in from Makefile.am and configure.ac autoreconf Run them as needed (autoreconf -fivm) Read Alexandre Duret-Lutz s Tutorial [1] A. D le, R. Levillain Development Tools 9 / 40
23 GNU Tools Autoconf for tc Automake for tc Programming Tools: Packages A set of packages to maintain packages: Autoconf package configuration [3] Automake package build [2] Libtool portable build of shared libs Gettext package internationalization Argp extended getopt Flex scanner generation Bison parser generation A. D le, R. Levillain Development Tools 10 / 40
24 GNU Tools Autoconf for tc Automake for tc Programming Tools: Packages A set of packages to maintain packages: Autoconf package configuration [3] Automake package build [2] Libtool portable build of shared libs Gettext package internationalization Argp extended getopt Flex scanner generation Bison parser generation A. D le, R. Levillain Development Tools 10 / 40
25 GNU Tools Autoconf for tc Automake for tc Programming Tools: Packages A set of packages to maintain packages: Autoconf package configuration [3] Automake package build [2] Libtool portable build of shared libs Gettext package internationalization Argp extended getopt Flex scanner generation Bison parser generation A. D le, R. Levillain Development Tools 10 / 40
26 GNU Tools Autoconf for tc Automake for tc Programming Tools: Packages A set of packages to maintain packages: Autoconf package configuration [3] Automake package build [2] Libtool portable build of shared libs Gettext package internationalization Argp extended getopt Flex scanner generation Bison parser generation A. D le, R. Levillain Development Tools 10 / 40
27 GNU Tools Autoconf for tc Automake for tc Programming Tools: Packages A set of packages to maintain packages: Autoconf package configuration [3] Automake package build [2] Libtool portable build of shared libs Gettext package internationalization Argp extended getopt Flex scanner generation Bison parser generation A. D le, R. Levillain Development Tools 10 / 40
28 GNU Tools Autoconf for tc Automake for tc Programming Tools: Packages A set of packages to maintain packages: Autoconf package configuration [3] Automake package build [2] Libtool portable build of shared libs Gettext package internationalization Argp extended getopt Flex scanner generation Bison parser generation A. D le, R. Levillain Development Tools 10 / 40
29 GNU Tools Autoconf for tc Automake for tc Programming Tools: Packages A set of packages to maintain packages: Autoconf package configuration [3] Automake package build [2] Libtool portable build of shared libs Gettext package internationalization Argp extended getopt Flex scanner generation Bison parser generation A. D le, R. Levillain Development Tools 10 / 40
30 Autoconf for tc 1 tc Tasks 2 GNU Tools Autoconf for tc Automake for tc 3
31 GNU Tools Autoconf for tc Automake for tc Autoconf files Configuring a package configure > config.log config.h.in -. v.-> config.h -. +-> config.status > make Makefile.in - -> Makefile - Preparing a package for distribution configure.ac > autoconf ----> configure > autoheader --> config.h.in aclocal.m A. D le, R. Levillain Development Tools 12 / 40
32 GNU Tools Autoconf for tc Automake for tc Autoconf files Configuring a package configure > config.log config.h.in -. v.-> config.h -. +-> config.status > make Makefile.in - -> Makefile - Preparing a package for distribution configure.ac > autoconf ----> configure > autoheader --> config.h.in aclocal.m A. D le, R. Levillain Development Tools 12 / 40
33 GNU Tools Autoconf for tc Automake for tc configure.ac 1: Initialization AC_PREREQ([2.64]) AC_INIT([LRDE Tiger Compiler], [1.29a], [tc]) # Auxiliary files. AC_CONFIG_AUX_DIR([build-aux]) AC_CONFIG_MACRO_DIR([build-aux]) # Automake. AM_INIT_AUTOMAKE([ check-news dist-bzip2 no-dist-gzip foreign color-tests parallel-tests nostdinc silent-rules -Wall]) AM_SILENT_RULES([yes]) A. D le, R. Levillain Development Tools 13 / 40
34 GNU Tools Autoconf for tc Automake for tc configure.ac 2: C++ Compiler # Look for a C++ compiler. AC_LANG([C++]) AC_PROG_CXX # Speed the compilation up. if test "$GXX" = yes; then CXXFLAGS="$CXXFLAGS -pipe" fi # Use good warnings. TC_CXX_WARNINGS([[-Wall], [-W], [-Wcast-align],...]) A. D le, R. Levillain Development Tools 14 / 40
35 GNU Tools Autoconf for tc Automake for tc configure.ac 3: Auxiliary Programs TC_PROG([flex], [>= 2.5.4], [FLEX], [Flex scanner generator]) AM_PROG_LEX TC_PROG([bison], [>= 2.4], [BISON], [Bison parser generator]) AC_CONFIG_FILES([build-aux/bison++], [chmod +x build-aux/bison++]) # We don t need static libraries, speed the compilation up. : ${enable_shared=no} AC_PROG_LIBTOOL TC_PROG([monoburg], [>= 1.0.5], [MONOBURG], [MonoBURG code generator generator]) AC_CONFIG_FILES([build-aux/monoburg++], [chmod +x build-aux/monoburg++]) TC_PROG([havm], [>=0.23], [HAVM], [The Tree Virtual Machine]) A. D le, R. Levillain Development Tools 15 / 40
36 GNU Tools Autoconf for tc Automake for tc configure.ac 4: Libraries AC_CONFIG_SUBDIRS([lib/argp]) TC_HEADER_BOOST([1.34]) # Boost.Conversion defines lexical_cast BOOST_CONVERSION BOOST_FOREACH BOOST_GRAPH BOOST_LAMBDA BOOST_PREPROCESSOR BOOST_STRING_ALGO BOOST_TRIBOOL BOOST_VARIANT A. D le, R. Levillain Development Tools 16 / 40
37 GNU Tools Autoconf for tc Automake for tc configure.ac 5: SWIG & tcsh TC_WITH_TCSH([with_tcsh=yes], [with_tcsh=no]) AM_CONDITIONAL([ENABLE_TCSH], [test x$with_tcsh = xyes]) AC_CONFIG_FILES([tcsh/Makefile tcsh/python/makefile tcsh/ruby/makefile]) AC_CONFIG_FILES([tcsh/run], [chmod +x tcsh/run]) A. D le, R. Levillain Development Tools 17 / 40
38 GNU Tools Autoconf for tc Automake for tc configure.ac 6: Modules MODULES= for module in cd $srcdir/src && ls do if test -f $srcdir/src/$module/tasks.hh; then MODULES="$MODULES $module"; fi done AC_SUBST([MODULES]) A. D le, R. Levillain Development Tools 18 / 40
39 GNU Tools Autoconf for tc Automake for tc configure.ac 7: File Creation # Ask for the creation of config.h. AM_CONFIG_HEADER([config.h]) # Ask for the creation of the Makefiles. AC_CONFIG_FILES([ Makefile lib/makefile src/makefile doc/makefile ]) # Instantiate the output files. AC_OUTPUT A. D le, R. Levillain Development Tools 19 / 40
40 Automake for tc 1 tc Tasks 2 GNU Tools Autoconf for tc Automake for tc 3
41 GNU Tools Autoconf for tc Automake for tc src/tc.mk 1: Common Options # Most headers are to be shipped and to be found in src/, e.g. # tasks/tasks.hh is shipped in $(top_srcdir)/src/task/tasks.hh. # Some are *built* in src, e.g., $(top_builddir)/src/modules.hh. AM_CPPFLAGS = -I$(top_srcdir)/lib AM_CPPFLAGS += -I$(top_srcdir)/src -I$(top_builddir)/src AM_CPPFLAGS += $(BOOST_CPPFLAGS) # Find the prelude. AM_CPPFLAGS += -DPKGDATADIR="\"$(pkgdatadir)\"" AM_CXXFLAGS = $(WARNING_CXXFLAGS) A. D le, R. Levillain Development Tools 21 / 40
42 GNU Tools Autoconf for tc Automake for tc src/tc.mk 2: Libraries # All our libraries, in the order of dependency. libregalloc_la = $(top_builddir)/src/regalloc/libregalloc.la libliveness_la = $(top_builddir)/src/liveness/libliveness.la [...] libtask_la = $(top_builddir)/src/task/libtask.la libmisc_la = $(top_builddir)/src/misc/libmisc.la libargp_la = $(top_builddir)/argp/libargp.la A. D le, R. Levillain Development Tools 22 / 40
43 GNU Tools Autoconf for tc Automake for tc src/tc.mk 3: Libraries Dependencies # All our libraries... libregalloc = $(libregalloc_la) libliveness = $(libliveness_la) [...] libtask = $(libtask_la) libmisc = $(libmisc_la) libargp = $(libargp_la) #... and their dependencies. libregalloc += $(libliveness) libliveness += $(libassem) [...] libast += $(libmisc) A. D le, R. Levillain Development Tools 23 / 40
44 GNU Tools Autoconf for tc Automake for tc src/makefile.am 1: Variables include $(top_srcdir)/src/tc.mk AUTOMAKE_OPTIONS = subdir-objects AM_DEFAULT_SOURCE_EXT =.cc BUILT_SOURCES = CLEANFILES = EXTRA_DIST = MAINTAINERCLEANFILES = TESTS = EXTRA_PROGRAMS = $(TESTS) dist_noinst_data = noinst_ltlibraries = RECHECK_LOGS = # Find the configuration headers. AM_CPPFLAGS += -I $(top_builddir) A. D le, R. Levillain Development Tools 24 / 40
45 GNU Tools Autoconf for tc Automake for tc src/makefile.am 2: Tasks TASKS = include task/local.mk include ast/local.mk [...] include regalloc/local.mk EXTRA_DIST += tiger_common.i A. D le, R. Levillain Development Tools 25 / 40
46 GNU Tools Autoconf for tc Automake for tc src/makefile.am 3: Building libtc lib_ltlibraries = libtc.la libtc_la_sources = version.hh nodist_libtc_la_sources = version.cc BUILT_SOURCES = $(nodist_libtc_la_sources) CLEANFILES += $(nodist_libtc_la_sources) ## Don t forget that if liba depends on libb, then libb must ## be specified *after* liba. ## ## We cannot use $(libfoo) because some libraries appear ## several times, resulting in a library comprising several ## definitions of some symbols. libtc_la_libadd = \ $(libregalloc_la) \... $(libargp_la) A. D le, R. Levillain Development Tools 26 / 40
47 GNU Tools Autoconf for tc Automake for tc src/makefile.am 4: Building tc bin_programs = tc dist_tc_sources = \ doc.hh \ $(TASKS) \ common.cc common.hh \ tc.cc tc_ldadd = $(libtask_la) libtc.la A. D le, R. Levillain Development Tools 27 / 40
48 GNU Tools Autoconf for tc Automake for tc src/bind/local.mk : Binding Names EXTRA_DIST += bind/tiger_bind.i noinst_ltlibraries += bind/libbind.la bind_libbind_la_sources = \ bind/binder.hh bind/binder.hxx bind/binder.cc \ bind/renamer.hh bind/renamer.hxx bind/renamer.cc \ bind/libbind.hh bind/libbind.cc TESTS += bind/test-bind bind_test_bind_ldadd = $(libbind) TASKS += bind/tasks.hh bind/tasks.cc A. D le, R. Levillain Development Tools 28 / 40
49 1 tc Tasks 2 3
50 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
51 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
52 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
53 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
54 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
55 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
56 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
57 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
58 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
59 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
60 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
61 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
62 Other developing tools Use warnings Use the assert macro Electric Fence DUMA Dmalloc AddressSanitizer Bound Checking GCC Mudflap (built in GCC) Purify (proprietary) GDB Valgrind DTrace Clang Static Analyzer (LLVM) A. D le, R. Levillain Development Tools 30 / 40
63 Mudflap int main () { int tab[10]; int i; for (i = 0; i <= 10; ++i) tab[i] = 0; return 0; } gcc -fmudflap -lmudflap bounds-violation.c A. D le, R. Levillain Development Tools 31 / 40
64 Mudflap env MUDFLAP_OPTIONS=-viol-abort./a.out ******* mudflap violation 1 (check/write): time= ptr=0xbfc35d34 size=44 pc=0xb77d13bd location= bounds-violation.c:8:5 (main) /usr/lib/libmudflap.so.0( mf_check+0x3d) [0xb77d13bd]./a.out(main+0xb7) [0x804883b] /usr/lib/libmudflap.so.0( wrap_main+0x49) [0xb77d0b89] Nearby object 1: checked region begins 0B into and ends 4B after mudflap object 0x8c7a080: name= bounds-violation.c:4:7 (main) tab bounds=[0xbfc35d34,0xbfc35d5b] size=40 area=stack check=0r/4w liveness=4 alloc time= pc=0xb77d0b2d number of nearby objects: 1 zsh: abort env MUDFLAP_OPTIONS=-viol-abort./a.out A. D le, R. Levillain Development Tools 32 / 40
65 Valgrind and Memory Violation #include <stdio.h> typedef struct list_s { int val; struct list_s *next; } list_t; list_t *list_new (int val, list_t *next) { list_t res = { val, next }; return &res; } void list_print (const list_t *const list) { if (list) printf ("%d\n", list->val), list_print (list->next); } int main (void) { list_print (list_new (2, list_new (1, list_new (0, NULL)))); return 0; } A. D le, R. Levillain Development Tools 33 / 40
66 Valgrind and Memory Leaks #include <stdio.h> #include <stdlib.h> typedef struct list_s { int val; struct list_s *next; } list_t; list_t *list_new (int val, list_t *next) { list_t *res = (list_t *) malloc (sizeof (list_t)); res->val = val; res->next = next; return res; } void list_print (const list_t *const list) { if (list) printf ("%d\n", list->val), list_print (list->next); } int main (void) { list_print (list_new (2, list_new (1, list_new (0, NULL)))); return 0; } A. D le, R. Levillain Development Tools 34 / 40
67 Valgrind and Memory Leaks gcc -g memory-leaks.c valgrind --leak-check=full./a.out ==9702== Memcheck, a memory error detector ==9702== Copyright (C) , and GNU GPL d, by Julian Seward et al. ==9702== Using Valgrind SVN-Debian and LibVEX; rerun with -h for copyright info ==9702== Command:./a.out ==9702== ==9702== ==9702== HEAP SUMMARY: ==9702== in use at exit: 24 bytes in 3 blocks ==9702== total heap usage: 3 allocs, 0 frees, 24 bytes allocated ==9702== ==9702== 24 (8 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record 3 of 3 ==9702== at 0x4023F50: malloc (vg_replace_malloc.c:236) ==9702== by 0x : list_new (memory-leaks.c:7) ==9702== by 0x804848D: main (memory-leaks.c:18) ==9702== ==9702== LEAK SUMMARY: ==9702== definitely lost: 8 bytes in 1 blocks ==9702== indirectly lost: 16 bytes in 2 blocks ==9702== possibly lost: 0 bytes in 0 blocks ==9702== still reachable: 0 bytes in 0 blocks ==9702== suppressed: 0 bytes in 0 blocks ==9702== ==9702== For counts of detected and suppressed errors, rerun with: -v ==9702== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 11 from 6) A. D le, R. Levillain Development Tools 35 / 40
68 A Clear Winner? Valgrind doesn t catch the previous Mudflap example. Padding Overrun into neighbor regions Mudflap doesn t know about uninitialized regions. A. D le, R. Levillain Development Tools 36 / 40
69 A Clear Winner? Valgrind doesn t catch the previous Mudflap example. Padding Overrun into neighbor regions Mudflap doesn t know about uninitialized regions. A. D le, R. Levillain Development Tools 36 / 40
70 A Clear Winner? Valgrind doesn t catch the previous Mudflap example. Padding Overrun into neighbor regions Mudflap doesn t know about uninitialized regions. A. D le, R. Levillain Development Tools 36 / 40
71 A Clear Winner? Valgrind doesn t catch the previous Mudflap example. Padding Overrun into neighbor regions Mudflap doesn t know about uninitialized regions. A. D le, R. Levillain Development Tools 36 / 40
72 Version Control Makes working in group a lot easier. Gives the possibility to travel back in time (e.g, to hunt bugs). Allows several, non-linear developing models (branches). Add some semantics to the development itself. Provides a kind of backup But cannot make up for the lack of a real backup solution! EPITA provides Git repositories for the Tiger project. :-) A. D le, R. Levillain Development Tools 37 / 40
73 Version Control Makes working in group a lot easier. Gives the possibility to travel back in time (e.g, to hunt bugs). Allows several, non-linear developing models (branches). Add some semantics to the development itself. Provides a kind of backup But cannot make up for the lack of a real backup solution! EPITA provides Git repositories for the Tiger project. :-) A. D le, R. Levillain Development Tools 37 / 40
74 Version Control Makes working in group a lot easier. Gives the possibility to travel back in time (e.g, to hunt bugs). Allows several, non-linear developing models (branches). Add some semantics to the development itself. Provides a kind of backup But cannot make up for the lack of a real backup solution! EPITA provides Git repositories for the Tiger project. :-) A. D le, R. Levillain Development Tools 37 / 40
75 Version Control Makes working in group a lot easier. Gives the possibility to travel back in time (e.g, to hunt bugs). Allows several, non-linear developing models (branches). Add some semantics to the development itself. Provides a kind of backup But cannot make up for the lack of a real backup solution! EPITA provides Git repositories for the Tiger project. :-) A. D le, R. Levillain Development Tools 37 / 40
76 Version Control Makes working in group a lot easier. Gives the possibility to travel back in time (e.g, to hunt bugs). Allows several, non-linear developing models (branches). Add some semantics to the development itself. Provides a kind of backup But cannot make up for the lack of a real backup solution! EPITA provides Git repositories for the Tiger project. :-) A. D le, R. Levillain Development Tools 37 / 40
77 Version Control Makes working in group a lot easier. Gives the possibility to travel back in time (e.g, to hunt bugs). Allows several, non-linear developing models (branches). Add some semantics to the development itself. Provides a kind of backup But cannot make up for the lack of a real backup solution! EPITA provides Git repositories for the Tiger project. :-) A. D le, R. Levillain Development Tools 37 / 40
78 Document with Doxygen Use comments to annotate code entities (namespaces, files, functions, classes, typedefs, etc.). Generate a hyper-text reference documentation. Several back-ends: HTML, PDF, RTF, etc. Use make doc in the Tiger Project. For more information, see A. D le, R. Levillain Development Tools 38 / 40
79 Document with Doxygen Use comments to annotate code entities (namespaces, files, functions, classes, typedefs, etc.). Generate a hyper-text reference documentation. Several back-ends: HTML, PDF, RTF, etc. Use make doc in the Tiger Project. For more information, see A. D le, R. Levillain Development Tools 38 / 40
80 Document with Doxygen Use comments to annotate code entities (namespaces, files, functions, classes, typedefs, etc.). Generate a hyper-text reference documentation. Several back-ends: HTML, PDF, RTF, etc. Use make doc in the Tiger Project. For more information, see A. D le, R. Levillain Development Tools 38 / 40
81 Document with Doxygen Use comments to annotate code entities (namespaces, files, functions, classes, typedefs, etc.). Generate a hyper-text reference documentation. Several back-ends: HTML, PDF, RTF, etc. Use make doc in the Tiger Project. For more information, see A. D le, R. Levillain Development Tools 38 / 40
82 Document with Doxygen Use comments to annotate code entities (namespaces, files, functions, classes, typedefs, etc.). Generate a hyper-text reference documentation. Several back-ends: HTML, PDF, RTF, etc. Use make doc in the Tiger Project. For more information, see A. D le, R. Levillain Development Tools 38 / 40
83 Document with Doxygen: type/libtype.hh /// \file type/libtype.hh /// \brief Declare the function exported by type module. #ifndef TYPE_LIBTYPE_HH # define TYPE_LIBTYPE_HH # include "misc/error.hh" # include "ast/fwd.hh" /// Type-checking an ast::ast. namespace type { /** \brief Check types in a (bound) AST. ** \param tree abstract syntax tree s root. ** \return synthesis of the errors possibly found. */ misc::error types_check (ast::ast& tree); } // namespace type #endif //!TYPE_LIBTYPE_HH A. D le, R. Levillain Development Tools 39 / 40
84 Bibliography I Alexandre Duret-Lutz. The Autotools Tutorial. Duret-Lutz/dl/autotools.pdf/, Alexandre Duret-Lutz and Tom Tromey. GNU Automake David J. MacKenzie, Ben Elliston, and Akim D le. GNU Autoconf A. D le, R. Levillain Development Tools 40 / 40
Autotools and GNU Build system
Autotools and GNU Build system YAKA 2008 EPITA 12/12/2006 YAKA 2008 (EPITA) Autotools and GNU Build system Page 1 / 13 Licence Copying is allowed Copyright c 2006 Benoit Sigoure Copyright c 2006 Alexandre
How To Create a GNU Autoconf / Automake Based Configure Script for Your Application Under Construction
How To Create a GNU Autoconf / Automake Based Configure Script for Your Application Under Construction by Prof.Dr. University of Applied Science Suedwestfalen, Germany 1 Table of Contents 1 Typography...
July 8, 2007 Jim Huang (jserv)
Introduction to Autotools July 8, 2007 Jim Huang (jserv) Overview Autoconf, Automake, and libtool working together Address portability, configuration needs Support GNU Coding Standards
Software Building (Sestavování aplikací)
Software Building (Sestavování aplikací) http://d3s.mff.cuni.cz Pavel Parízek parizek@d3s.mff.cuni.cz CHARLES UNIVERSITY IN PRAGUE faculty of mathematics and physics Outline Maven NuGet Gradle GNU build
COMP 2400 UNIX Tools
COMP 2400 UNIX Tools Christian Grothoff christian@grothoff.org http://grothoff.org/christian/ 1 Makefile Basics make reads instructions from a file Makefile. A Makefile is essentially a list of rules.
Autotools Tutorial. Mengke HU. ASPITRG Group Meeting. ECE Department Drexel University
Autotools Tutorial Mengke HU ECE Department Drexel University ASPITRG Group Meeting Outline 1 Introduction 2 GNU Coding standards 3 Autoconf 4 Automake 5 Libtools 6 Demonstration The Basics of Autotools
Make was originally a Unix tool from 1976, but it has been re-implemented several times, notably as GNU Make.
make Make was originally a Unix tool from 1976, but it has been re-implemented several times, notably as GNU Make. Make accepts a Makefile, which is a strictly formatted file detailing a series of desired
Beyond Makefiles: Autotools and the GNU Build System
SEA : Autotools and the GNU Build System Patrick Nichols Software Engineer CISL Consulting Group UCAR SEA December 10, 2015 Why do we need more tools? Diversity! 1. Compilers, programming languages and
Memory Analysis tools
Memory Analysis tools PURIFY The Necessity TOOL Application behaviour: Crashes intermittently Uses too much memory Runs too slowly Isn t well tested Is about to ship You need something See what your code
Memory Allocation in C C Programming and Software Tools. N.C. State Department of Computer Science
Memory Allocation in C C Programming and Software Tools N.C. State Department of Computer Science The Easy Way Java (JVM) automatically allocates and reclaims memory for you, e.g... Removed object is implicitly
GNU Autotools Tutorial
GNU Autotools Tutorial Copyright c 2010 Nils Turner Chapter 1: Introduction 1 1 Introduction Those of us that have installed software from source code at some time in our career have no doubt become familiar
12. Debugging. Overview. COMP1917: Computing 1. Developing Programs. The Programming Cycle. Programming cycle. Do-it-yourself debugging
COMP1917 12s2 Debugging 1 COMP1917: Computing 1 12. Debugging Overview Programming cycle Do-it-yourself debugging Debugging withgdb Nastier bugs Memory leaks COMP1917 12s2 Debugging 2 Developing Programs
CSE 333 Midterm Exam Sample Solution 7/28/14
Question 1. (20 points) C programming. For this question implement a C function contains that returns 1 (true) if a given C string appears as a substring of another C string starting at a given position.
Introduction to the Tiger Project
Introduction to the Tiger Project Akim Demaille Étienne Renault Roland Levillain first.last@lrde.epita.fr EPITA École Pour l Informatique et les Techniques Avancées January 29th, 2018 Context and Motivation
CSE 374 Final Exam 3/15/17. Name UW ID#
Name UW ID# There are 10 questions worth a total of 110 points. Please budget your time so you get to all of the questions. Keep your answers brief and to the point. The exam is closed book, closed notes,
The Makefile utility. (Extract from the slides by Terrance E. Boult
The Makefile utility (Extract from the slides by Terrance E. Boult http://vast.uccs.edu/~tboult/) Motivation Small programs single file Not so small programs : Many lines of code Multiple components More
CSCI-1200 Data Structures Spring 2016 Lecture 6 Pointers & Dynamic Memory
Announcements CSCI-1200 Data Structures Spring 2016 Lecture 6 Pointers & Dynamic Memory There will be no lecture on Tuesday, Feb. 16. Prof. Thompson s office hours are canceled for Monday, Feb. 15. Prof.
Why Use the Autotools?...xviii Acknowledgments... xx I Wish You the Very Best... xx
CONTENTS IN DETAIL FOREWORD by Ralf Wildenhues xv PREFACE xvii Why Use the?...xviii Acknowledgments... xx I Wish You the Very Best... xx INTRODUCTION xxi Who Should Read This Book... xxii How This Book
Intermediate Programming, Spring 2017*
600.120 Intermediate Programming, Spring 2017* Misha Kazhdan *Much of the code in these examples is not commented because it would otherwise not fit on the slides. This is bad coding practice in general
The Valgrind Memory Checker. (i.e., Your best friend.)
The Valgrind Memory Checker. (i.e., Your best friend.) Dept of Computing Science University of Alberta Small modifications by Stef Nychka, Mar. 2006 5th March 2006 Attribution. Introduction Some of the
Debugging (Part 2) 1
Debugging (Part 2) 1 Programming in the Large Steps Design & Implement Program & programming style (done) Common data structures and algorithms Modularity Building techniques & tools (done) Test Testing
CSE 374 Final Exam 3/15/17 Sample Solution. Question 1. (8 points) Suppose we have the following two statements in a C program:
Question 1. (8 points) Suppose we have the following two statements in a C program: int *x = malloc(sizeof(int)); int *y = malloc(sizeof(int)); For each of the following expressions, write true if the
Princeton University Computer Science 217: Introduction to Programming Systems. Data Structures
Princeton University Computer Science 217: Introduction to Programming Systems Data Structures 1 Goals of this Lecture Help you learn (or refresh your memory) about: Common data structures: linked lists
DEBUGGING: DYNAMIC PROGRAM ANALYSIS
DEBUGGING: DYNAMIC PROGRAM ANALYSIS WS 2017/2018 Martina Seidl Institute for Formal Models and Verification System Invariants properties of a program must hold over the entire run: integrity of data no
Managing Code Variants
Steven J Zeil March 19, 2013 Contents 1 Problems 2 2 AUTOCONF 8 3 Dynamic Loading 11 1 1 Problems Code Variations Environment management, Previously identified as common SCM problems: Coping with change
Managing Code Variants
Steven J Zeil March 19, 2013 Contents 1 Problems 2 2 AUTOCONF 9 3 Dynamic Loading 14 1 1 Problems Code Variations Environment management, Previously identified as common SCM problems: Coping with change
Key C Topics: Tutorial Pointers, Dynamic Memory allocation, Valgrind and Makefile CS370
Key C Topics: Tutorial Pointers, Dynamic Memory allocation, Valgrind and Makefile CS370 Outline Pointers in C & and * operators Pointers with Arrays and Strings Dynamic memory allocation malloc() and free()
The Valgrind Memory Checker. (i.e., Your best friend.)
The Valgrind Memory Checker. (i.e., Your best friend.) Dept of Computing Science University of Alberta modifications by Stef Nychka October 24, 2007 Attribution. Introduction Some of the material in this
CSE 15L Winter Midterm :) Review
CSE 15L Winter 2015 Midterm :) Review Makefiles Makefiles - The Overview Questions you should be able to answer What is the point of a Makefile Why don t we just compile it again? Why don t we just use
ESTABLISHED Paul Kunz SLAC. Overview. Examples. Expose the downsides. Benefits. Risks and Costs. Building with Automake 1 Paul F.
Building with Automake Paul Kunz SLAC Overview Examples Expose the downsides Benefits Risks and Costs Building with Automake 1 Paul F. Kunz Overview Primary targets build in developer s working directory
The GNU configure and build system
!"$#% &(') *+ The GNU configure and build system Ian Lance Taylor Copyright c 1998 Cygnus Solutions Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice
A Set of Tools to Teach Compiler Construction
A Set of Tools to Teach Compiler Construction Akim Demaille Roland Levillain Benoît Perrot EPITA Research and Development Laboratory (LRDE) Paris, France 13th Annual Conference on Innovation and Technology
valgrind overview: runtime memory checker and a bit more What can we do with it?
Valgrind overview: Runtime memory checker and a bit more... What can we do with it? MLUG Mar 30, 2013 The problem When do we start thinking of weird bug in a program? The problem When do we start thinking
CptS 360 (System Programming) Unit 4: Debugging
CptS 360 (System Programming) Unit 4: Debugging Bob Lewis School of Engineering and Applied Sciences Washington State University Spring, 2018 Motivation You re probably going to spend most of your code
CSCI-243 Exam 1 Review February 22, 2015 Presented by the RIT Computer Science Community
CSCI-243 Exam 1 Review February 22, 2015 Presented by the RIT Computer Science Community http://csc.cs.rit.edu History and Evolution of Programming Languages 1. Explain the relationship between machine
Use Dynamic Analysis Tools on Linux
Use Dynamic Analysis Tools on Linux FTF-SDS-F0407 Gene Fortanely Freescale Software Engineer Catalin Udma A P R. 2 0 1 4 Software Engineer, Digital Networking TM External Use Session Introduction This
Scientific Programming in C IX. Debugging
Scientific Programming in C IX. Debugging Susi Lehtola 13 November 2012 Debugging Quite often you spend an hour to write a code, and then two hours debugging why it doesn t work properly. Scientific Programming
CSci 4061 Introduction to Operating Systems. Programs in C/Unix
CSci 4061 Introduction to Operating Systems Programs in C/Unix Today Basic C programming Follow on to recitation Structure of a C program A C program consists of a collection of C functions, structs, arrays,
The WAF build system
Sebastian Jeltsch Electronic Vision(s) Kirchhoff Institute for Physics Ruprecht-Karls-Universität Heidelberg 31. August 2010 Sebastian Jeltsch 31. August 2010 1 / 19 Introduction WorkBuildflow Sebastian
The assignment requires solving a matrix access problem using only pointers to access the array elements, and introduces the use of struct data types.
C Programming Simple Array Processing The assignment requires solving a matrix access problem using only pointers to access the array elements, and introduces the use of struct data types. Both parts center
Both parts center on the concept of a "mesa", and make use of the following data type:
C Programming Simple Array Processing This assignment consists of two parts. The first part focuses on array read accesses and computational logic. The second part requires solving the same problem using
{C} Tools of the Trade
{C} Tools of the Trade make Building Software 3 gcc is our compiler Turns C code into machine code ar is our librarian Gathers machine code files into groups called libraries But calling these over and
TI2725-C, C programming lab, course
Valgrind tutorial Valgrind is a tool which can find memory leaks in your programs, such as buffer overflows and bad memory management. This document will show per example how Valgrind responds to buggy
Recitation: Cache Lab & C
15-213 Recitation: Cache Lab & C Jack Biggs 16 Feb 2015 Agenda Buffer Lab! C Exercises! C Conventions! C Debugging! Version Control! Compilation! Buffer Lab... Is due soon. So maybe do it soon Agenda Buffer
NetCDF Build and Test System. Ed Hartnett, 1/25/8
NetCDF Build and Test System Ed Hartnett, 1/25/8 Outline NetCDF Repository Building NetCDF Testing NetCDF NetCDF Code Repository We use cvs for netcdf code repository. The cvs repository module is called
Scientific Programming in C IV. Pointers
Scientific Programming in C IV. Pointers Susi Lehtola 1 November 2012 Pointers The feature at the heart of C are pointers, which are simply pointers to memory addresses. Scientific Programming in C, fall
CSCI-243 Exam 2 Review February 22, 2015 Presented by the RIT Computer Science Community
CSCI-43 Exam Review February, 01 Presented by the RIT Computer Science Community http://csc.cs.rit.edu C Preprocessor 1. Consider the following program: 1 # include 3 # ifdef WINDOWS 4 # include
GNU Automake. For version , 1 February David MacKenzie Tom Tromey Alexandre Duret-Lutz
GNU Automake For version 1.11.3, 1 February 2012 David MacKenzie Tom Tromey Alexandre Duret-Lutz This manual is for GNU Automake (version 1.11.3, 1 February 2012), a program that creates GNU standards-compliant
CSCI-1200 Data Structures Fall 2015 Lecture 6 Pointers & Dynamic Memory
CSCI-1200 Data Structures Fall 2015 Lecture 6 Pointers & Dynamic Memory Announcements: Test 1 Information Test 1 will be held Monday, September 21st, 2015 from 6-:50pm. Students have been randomly assigned
Pointers and Memory Management
Pointers and Memory Management Timo Karvi 2013 Timo Karvi () Pointers and Memory Management 2013 1 / 58 Memory and C I In most modern computers, main memory is divided into bytes, with each byte capable
Learning ctools and GammaLib development in an hour
Learning ctools and GammaLib development in an hour Introduction to 6 th ctools coding sprint Jürgen Knödlseder (IRAP) What I expect you know How to write C++ and/or Python code How to use Git Our GitLab
Praktische Aspekte der Informatik
Praktische Aspekte der Informatik Moritz Mühlhausen Prof. Marcus Magnor Optimization valgrind, gprof, and callgrind Further Reading Warning! The following slides are meant to give you a very superficial
6.S096: Introduction to C/C++
6.S096: Introduction to C/C++ Frank Li, Tom Lieber, Kyle Murray Lecture 4: Data Structures and Debugging! January 17, 2012 Today Memory Leaks and Valgrind Tool Structs and Unions Opaque Types Enum and
FOLLOW ALONG WITH THE EXAMPLES
FOLLOW ALONG WITH THE EXAMPLES $ git clone https://gitlab.com/jtfrey/unix-software-dev.git ( or "git pull" if you cloned at last session ) $ git checkout tags/session2 $ ls -l total 8 -rw-r--r-- 1 frey
Subprograms. Akim D le Étienne Renault Roland Levillain EPITA École Pour l Informatique et les Techniques Avancées
Subprograms Akim Demaille Étienne Renault Roland Levillain first.last@lrde.epita.fr EPITA École Pour l Informatique et les Techniques Avancées June 1, 2017 Subprograms 1 Routines 2 Argument passing 3 Functions
These steps may include:
Build Tools 1 Build Tools Building a program for a large project is usually managed by a build tool that controls the various steps involved. These steps may include: 1. Compiling source code to binaries
Brief History of Automake
Brief History of Automake David MacKenzie Tom Tromey Alexandre Duret-Lutz This manual describes (part of) the history of GNU Automake, a program that creates GNU standards-compliant Makefiles from template
A Capacity: 10 Usage: 4 Data:
Creating a Data Type in C Integer Set For this assignment, you will use the struct mechanism in C to implement a data type that represents sets of integers. A set can be modeled using the C struct: struct
Projet 0 - Correc,on. Structures de données et algorithmes
Projet 0 - Correc,on Structures de données et algorithmes Code de base #include #define uint unsigned int #define N 101 int f(int m, int M, uint* s) *s ^= (uint)(*s
Exception Namespaces C Interoperability Templates. More C++ David Chisnall. March 17, 2011
More C++ David Chisnall March 17, 2011 Exceptions A more fashionable goto Provides a second way of sending an error condition up the stack until it can be handled Lets intervening stack frames ignore errors
PRINCIPLES OF OPERATING SYSTEMS
PRINCIPLES OF OPERATING SYSTEMS Tutorial-1&2: C Review CPSC 457, Spring 2015 May 20-21, 2015 Department of Computer Science, University of Calgary Connecting to your VM Open a terminal (in your linux machine)
Linked data structures. EECS 211 Winter 2019
Linked data structures EECS 211 Winter 2019 2 Initial code setup $ cd eecs211 $ curl $URL211/lec/07linked.tgz tar zx $ cd 07linked Preliminaries 3 4 Two views on malloc and free The client/c view: malloc(n)
CSCI-1200 Data Structures Spring 2013 Lecture 7 Templated Classes & Vector Implementation
CSCI-1200 Data Structures Spring 2013 Lecture 7 Templated Classes & Vector Implementation Review from Lectures 5 & 6 Arrays and pointers Different types of memory ( automatic, static, dynamic) Dynamic
Build automation. CSE260, Computer Science B: Honors Stony Brook University
Build automation CSE260, Computer Science B: Honors Stony Brook University http://www.cs.stonybrook.edu/~cse260 2 Build Automation Build automation is the act of scripting or automating a wide variety
System Assertions. Andreas Zeller
System Assertions Andreas Zeller System Invariants Some properties of a program must hold over the entire run: must not access data of other processes must handle mathematical exceptions must not exceed
18-642: Code Style for Compilers
18-642: Code Style for Compilers 9/25/2017 1 Anti-Patterns: Coding Style: Language Use Code compiles with warnings Warnings are turned off or over-ridden Insufficient warning level set Language safety
libsbml An Overview and Brief Tutorial Benjamin J. Bornstein 1,2 Jet Propulsion Laboratory, Machine Learning Systems
libsbml An Overview and Brief Tutorial Benjamin J. Bornstein 1,2 1 Jet Propulsion Laboratory, Machine Learning Systems 2 California Institute of Technology Presented at the 7 th Forum on Software Platforms
CS11 Advanced C++ Fall Lecture 4
CS11 Advanced C++ Fall 2006-2007 Lecture 4 Today s Topics Using make to automate build tasks Using doxygen to generate API docs Build-Automation Standard development cycle: Write more code Compile Test
Study of tools used in build process
Study of tools used in build process Sameera Deshpande November 16, 2005 Contents 1 Introduction 2 1.1 Introduction to configure and build process................. 2 1.2 Configure and Build Process.........................
Guidelines for Writing C Code
Guidelines for Writing C Code Issue 01-bugfix Martin Becker Institute for Real-Time Computer Systems (RCS) Technische Universität München becker@rcs.ei.tum.de June 9, 2014 Contents 1 Introduction 1 2 Pragmatic
The Scanner and The Parser
The Scanner and The Parser Akim Demaille Étienne Renault Roland Levillain first.last@lrde.epita.fr EPITA École Pour l Informatique et les Techniques Avancées January 25, 2018 The Scanner and The Parser
CSE 160 Discussion Section. Winter 2017 Week 3
CSE 160 Discussion Section Winter 2017 Week 3 Homework 1 - Recap & a few points ComputeMandelbrotPoint func() in smdb.cpp does the job serially. You will have to do the same task in parallel manner in
82V391x / 8V893xx WAN PLL Device Families Device Driver User s Guide
82V391x / 8V893xx WAN PLL Device Families Device Driver Version 1.2 April 29, 2014 Table of Contents 1. Introduction... 1 2. Software Architecture... 2 2.1. Overview... 2 2.2. Hardware Abstraction Layer
CS354R: Game Technology
CS354R: Game Technology DevOps and Quality Assurance Fall 2018 What is DevOps? Development Operations Backend facilitation of development Handles local and remote hardware Maintains build infrastructure
CSE 333 Midterm Exam July 24, Name UW ID#
Name UW ID# There are 6 questions worth a total of 100 points. Please budget your time so you get to all of the questions. Keep your answers brief and to the point. The exam is closed book, closed notes,
Lecture 19 Notes Data Structures in C
Lecture 19 Notes Data Structures in C 15-122: Principles of Imperative Computation (Fall 2015) Rob Simmons In this lecture, we will begin our transition to C. In many ways, the lecture is therefore about
MRO Delay Line. Coding and Documentation Guidelines for Prototype Delay Line Software. John Young. rev June 2007
MRO Delay Line Coding and Documentation Guidelines for Prototype Delay Line Software John Young rev 0.5 21 June 2007 Cavendish Laboratory Madingley Road Cambridge CB3 0HE UK Objective To propose a set
18-642: Code Style for Compilers
18-642: Code Style for Compilers 9/6/2018 2017-2018 Philip Koopman Programming can be fun, so can cryptography; however they should not be combined. Kreitzberg and Shneiderman 2017-2018 Philip Koopman
ICHEC. Using Valgrind. Using Valgrind :: detecting memory errors. Introduction. Program Compilation TECHNICAL REPORT
ICHEC TECHNICAL REPORT Mr. Ivan Girotto ICHEC Computational Scientist Stoney Compute Node Bull Novascale R422-E2 Using Valgrind :: detecting memory errors Valgrind is a suite of command line tools both
Kurt Schmidt. October 30, 2018
to Structs Dept. of Computer Science, Drexel University October 30, 2018 Array Objectives to Structs Intended audience: Student who has working knowledge of Python To gain some experience with a statically-typed
CSCI 171 Chapter Outlines
Contents CSCI 171 Chapter 1 Overview... 2 CSCI 171 Chapter 2 Programming Components... 3 CSCI 171 Chapter 3 (Sections 1 4) Selection Structures... 5 CSCI 171 Chapter 3 (Sections 5 & 6) Iteration Structures
Module 2: GNU Tools and Compilation Process Introduction to GCC and History The original GNU C Compiler is developed by Richard Stallman in 1984 to create a complete UNIX like operating systems as free
GLIMMER, Version Control and Build Systems
Outlines GLIMMER, Version Control and Build Systems Magnus Hagdorn School of GeoSciences University of Edinburgh December 5, 2005 Outlines Outline of Part I Unix Directory Structure Installing GLIMMER
Lecture 2. Xiaoguang Wang. January 16th, 2014 STAT 598W. (STAT 598W) Lecture 2 1 / 41
Lecture 2 Xiaoguang Wang STAT 598W January 16th, 2014 (STAT 598W) Lecture 2 1 / 41 Outline 1 GNU compiler and debugger 2 Pointers and Arrays 3 Structures 4 Compilation Process 5 Exercises (STAT 598W) Lecture
Creating a String Data Type in C
C Programming Creating a String Data Type in C For this assignment, you will use the struct mechanism in C to implement a data type that models a character string: struct _String { char data; dynamically-allocated
C Review. MaxMSP Developers Workshop Summer 2009 CNMAT
C Review MaxMSP Developers Workshop Summer 2009 CNMAT C Syntax Program control (loops, branches): Function calls Math: +, -, *, /, ++, -- Variables, types, structures, assignment Pointers and memory (***
System Assertions. Your Submissions. Oral Exams FEBRUARY FEBRUARY FEBRUARY
System Assertions Andreas Zeller 1 Your Submissions Program must behave exactly as specified (i.e., input, output, flags, etc.) Program must use recent Python 2 version (i.e., Python 2.6 installed in CIP
Mobile Location Protocol
Mobile Location Protocol User Guide Petr VLFčIL Mobile Location Protocol: User Guide Petr VLFčIL Copyright 2009 Petr VLFčIL Licensed Materials. All rights reserved. Materials are provided subject to Terms
CSE 333 Midterm Exam 5/10/13
Name There are 5 questions worth a total of 100 points. Please budget your time so you get to all of the questions. Keep your answers brief and to the point. The exam is closed book, closed notes, closed
The Design and Implementation of Gnu Compiler Collection
The Design and Implementation of Gnu Compiler Collection Uday Khedker (www.cse.iitb.ac.in/ uday) Department of Computer Science and Engineering, Indian Institute of Technology, Bombay July 2008 Part 1
Deep C. Multifile projects Getting it running Data types Typecasting Memory management Pointers. CS-343 Operating Systems
Deep C Multifile projects Getting it running Data types Typecasting Memory management Pointers Fabián E. Bustamante, Fall 2004 Multifile Projects Give your project a structure Modularized design Reuse
CS558 Programming Languages
CS558 Programming Languages Winter 2017 Lecture 4a Andrew Tolmach Portland State University 1994-2017 Semantics and Erroneous Programs Important part of language specification is distinguishing valid from
New features in AddressSanitizer. LLVM developer meeting Nov 7, 2013 Alexey Samsonov, Kostya Serebryany
New features in AddressSanitizer LLVM developer meeting Nov 7, 2013 Alexey Samsonov, Kostya Serebryany Agenda AddressSanitizer (ASan): a quick reminder New features: Initialization-order-fiasco Stack-use-after-scope
Programming in C S c o t t S c h r e m m e r
Programming in C S c o t t S c h r e m m e r Outline Introduction Data Types and structures Pointers, arrays and dynamic memory allocation Functions and prototypes input/output comparisons compiling/makefiles/debugging
Improving Error Checking and Unsafe Optimizations using Software Speculation. Kirk Kelsey and Chen Ding University of Rochester
Improving Error Checking and Unsafe Optimizations using Software Speculation Kirk Kelsey and Chen Ding University of Rochester Outline Motivation Brief problem statement How speculation can help Our software
Recitation: C Review. TA s 20 Feb 2017
15-213 Recitation: C Review TA s 20 Feb 2017 Agenda Logistics Attack Lab Conclusion C Assessment C Programming Style C Exercise Cache Lab Overview Appendix: Valgrind Clang / LLVM Cache Structure Logistics
ANITA S SUPER AWESOME RECITATION SLIDES
ANITA S SUPER AWESOME RECITATION SLIDES 15/18-213: Introduction to Computer Systems Dynamic Memory Allocation Anita Zhang, Section M UPDATES Cache Lab style points released Don t fret too much Shell Lab
Build Tools. Stefan Vigerske COIN-OR Workshop October 15, 2018
Build Tools https://projects.coin-or.org/buildtools Stefan Vigerske COIN-OR Workshop October 15, 2018 BuildTools 0.5 0.8 COIN-OR BuildTools project a set of scripts to utilize Autotools (GNU Build System)
Computer Labs: Debugging
Computer Labs: Debugging 2 o MIEIC Pedro F. Souto (pfs@fe.up.pt) October 29, 2012 Bugs and Debugging Problem To err is human This is specially true when the human is a programmer :( Solution There is none.
1 A Brief Introduction To GDB
1 A Brief Introduction To GDB GDB, the GNU Project debugger, allows you to see what is going on inside another program while it executes or what another program was doing at the moment it crashed. GDB