Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Deep C (and C++)
                                     by Olve Maudal and Jon Jagger




                                  ...
Suppose you are about to interview a candidate for a position as
C programmer for various embedded platforms. As part of t...
Suppose you are about to interview a candidate for a position as
C programmer for various embedded platforms. As part of t...
Suppose you are about to interview a candidate for a position as
C programmer for various embedded platforms. As part of t...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main()
                     {
...
What will happen if you try to compile, link and run this program?
                     int main(void)
                   ...
What will happen if you try to compile, link and run this program?
                      int main(void)
                  ...
What will happen if you try to compile, link and run this program?
                     int main(void)
                   ...
What will happen if you try to compile, link and run this program?
                     int main(void)
                   ...
What will happen if you try to compile, link and run this program?
                     int main(void)
                   ...
What will happen if you try to compile, link and run this program?
                     int main(void)
                   ...
What will happen if you try to compile, link and run this program?

                     int main(void)
                  ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
What will happen if you try to compile, link and run this program?
                     #include <stdio.h>

              ...
Is there any difference between these two candidates?
Is there any difference between these two candidates?




 Not much, yet, but I really like her answers so far.
Now suppose they are not really candidates. Perhaps they
are stereotypes for engineers working in your organization?
Now suppose they are not really candidates. Perhaps they
are stereotypes for engineers working in your organization?
Now suppose they are not really candidates. Perhaps they
   are stereotypes for engineers working in your organization?


...
Let’s find out how deep their knowledge of C and C++ is...
Let’s find out how deep their knowledge of C and C++ is...
#include <stdio.h>

void foo(void)
{
    int a = 3;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo(...
#include <stdio.h>       it will print 4, then 4, then 4

void foo(void)
{
    int a = 3;
    ++a;
    printf("%dn", a);
}...
#include <stdio.h>

void foo(void)
{
    int a = 3;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo(...
#include <stdio.h>

void foo(void)
{
    static int a = 3;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
 ...
#include <stdio.h>       it will print 4, then 5, then 6

void foo(void)
{
    static int a = 3;
    ++a;
    printf("%dn"...
#include <stdio.h>

void foo(void)
{
    static int a = 3;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
 ...
#include <stdio.h>

void foo(void)
{
    static int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    f...
#include <stdio.h>

void foo(void)
{
    static int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    f...
#include <stdio.h>

void foo(void)
{
    static int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    f...
#include <stdio.h>       eh, is it undefined? do you get garbage values?

void foo(void)
{
    static int a;
    ++a;
    p...
#include <stdio.h>       eh, is it undefined? do you get garbage values?

void foo(void)
                                  ...
#include <stdio.h>       eh, is it undefined? do you get garbage values?

void foo(void)
                                  ...
#include <stdio.h>       eh, is it undefined? do you get garbage values?

void foo(void)
                                  ...
#include <stdio.h>       eh, is it undefined? do you get garbage values?

void foo(void)
                                  ...
#include <stdio.h>       eh, is it undefined? do you get garbage values?

void foo(void)
                                  ...
#include <stdio.h>

void foo(void)
{
    static int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    f...
#include <stdio.h>

void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
 ...
#include <stdio.h>

void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
 ...
#include <stdio.h>

void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
 ...
Now you get 1, then 1, then 1
#include <stdio.h>

void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(v...
Now you get 1, then 1, then 1
#include <stdio.h>
                         Ehm, why do you think that will happen?
void foo...
Now you get 1, then 1, then 1
#include <stdio.h>
                            Ehm, why do you think that will happen?
void ...
Now you get 1, then 1, then 1
#include <stdio.h>
                            Ehm, why do you think that will happen?
void ...
Now you get 1, then 1, then 1
#include <stdio.h>
                            Ehm, why do you think that will happen?
void ...
Now you get 1, then 1, then 1
#include <stdio.h>
                            Ehm, why do you think that will happen?
void ...
Now you get 1, then 1, then 1
#include <stdio.h>
                                Ehm, why do you think that will happen?
v...
Now you get 1, then 1, then 1
#include <stdio.h>
                                Ehm, why do you think that will happen?
v...
Now you get 1, then 1, then 1
#include <stdio.h>
                                Ehm, why do you think that will happen?
v...
#include <stdio.h>

void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
 ...
#include <stdio.h>       Why do you think static variables are set to 0,
                         while auto variables are...
#include <stdio.h>       Why do you think static variables are set to 0,
                         while auto variables are...
#include <stdio.h>       Why do you think static variables are set to 0,
                         while auto variables are...
#include <stdio.h>       Why do you think static variables are set to 0,
                         while auto variables are...
#include <stdio.h>       Why do you think static variables are set to 0,
                         while auto variables are...
#include <stdio.h>       Why do you think static variables are set to 0,
                         while auto variables are...
#include <stdio.h>        Why do you think static variables are set to 0,
                          while auto variables a...
#include <stdio.h>

void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
 ...
#include <stdio.h>


void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
...
#include <stdio.h>



void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();...
#include <stdio.h>

static int a;

void foo(void)
{
    int a;
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo(...
#include <stdio.h>

static int a;

void foo(void)
{

    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo...
#include <stdio.h>

static int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo(...
#include <stdio.h>

static int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo(...
#include <stdio.h>

static int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo(...
1, 2, 3
#include <stdio.h>

static int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
...
1, 2, 3
#include <stdio.h>
                           ok, why?
static int a;

void foo(void)
{
    ++a;
    printf("%dn", ...
1, 2, 3
#include <stdio.h>
                                               ok, why?
static int a;
                         ...
1, 2, 3
#include <stdio.h>
                                               ok, why?
static int a;
                         ...
1, 2, 3
#include <stdio.h>
                                               ok, why?
static int a;
                         ...
#include <stdio.h>

static int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo(...
#include <stdio.h>

int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
    ...
#include <stdio.h>

int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
    ...
#include <stdio.h>

int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
    ...
garbage, garbage, garbage
#include <stdio.h>

int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
...
garbage, garbage, garbage
#include <stdio.h>
                             why do you think that?
int a;

void foo(void)
{
...
garbage, garbage, garbage
#include <stdio.h>
                              why do you think that?
int a;
                 ...
garbage, garbage, garbage
#include <stdio.h>
                              why do you think that?
int a;
                 ...
garbage, garbage, garbage
#include <stdio.h>
                              why do you think that?
int a;
                 ...
garbage, garbage, garbage
#include <stdio.h>
                              why do you think that?
int a;
                 ...
garbage, garbage, garbage
#include <stdio.h>
                                           why do you think that?
int a;
    ...
garbage, garbage, garbage
#include <stdio.h>
                                               why do you think that?
int a;
...
garbage, garbage, garbage
#include <stdio.h>
                                               why do you think that?
int a;
...
#include <stdio.h>

int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
    ...
#include <stdio.h>

int a;

void foo(void)
{
    ++a;
    printf("%dn", a);
}

int main(void)
{
    foo();
    foo();
    ...
it will print 1, 2, 3, the variable is still statically
#include <stdio.h>                allocated and it will be set to ...
it will print 1, 2, 3, the variable is still statically
#include <stdio.h>                allocated and it will be set to ...
it will print 1, 2, 3, the variable is still statically
#include <stdio.h>                         allocated and it will b...
I am now going to show you something cool!
I am now going to show you something cool!


#include <stdio.h>

void foo(void)
{
    int a;
    printf("%dn", a);
}

void...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out

void foo(void)
{
   ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                $ cc foo.c && ./a.out
                     ...
I am now going to show you something cool!


#include <stdio.h>                 $ cc foo.c && ./a.out
                    ...
#include <stdio.h>       $ cc -O foo.c && ./a.out
                         1606415608
void foo(void)
{
    int a;
    prin...
#include <stdio.h>       $ cc -O foo.c && ./a.out
                         1606415608
void foo(void)
{
    int a;
    prin...
#include <stdio.h>       $ cc -O foo.c && ./a.out
                         1606415608
void foo(void)
{
    int a;         ...
So what about this code snippet?
So what about this code snippet?

#include <stdio.h>

void foo(void)
{
    int a = 41;
    a = a++;
    printf("%dn", a);
...
#include <stdio.h>

void foo(void)
{
    int a = 41;
    a = a++;
    printf("%dn", a);
}

int main(void)
{
    foo();
}
#include <stdio.h>       I would never write code like that.

void foo(void)
{
    int a = 41;
    a = a++;
    printf("%d...
#include <stdio.h>       I would never write code like that.

void foo(void)
                                      That’s ...
#include <stdio.h>       I would never write code like that.

void foo(void)
                                      That’s ...
#include <stdio.h>       I would never write code like that.

void foo(void)
                                      That’s ...
#include <stdio.h>       I would never write code like that.

void foo(void)
                                      That’s ...
#include <stdio.h>       I would never write code like that.

void foo(void)
                                      That’s ...
#include <stdio.h>       I would never write code like that.

void foo(void)
                                      That’s ...
#include <stdio.h>       I would never write code like that.

void foo(void)
                                      That’s ...
#include <stdio.h>                 I would never write code like that.

void foo(void)
                                   ...
#include <stdio.h>

void foo(void)
{
    int a = 41;
    a = a++;
    printf("%dn", a);
}

int main(void)
{
    foo();
}
#include <stdio.h>

void foo(void)
{
    int a = 41;
    a = a++;
    printf("%dn", a);
}

int main(void)
{
    foo();
}
#include <stdio.h>       a gets an undefined value

void foo(void)
{
    int a = 41;
    a = a++;
    printf("%dn", a);
}

...
#include <stdio.h>        a gets an undefined value

void foo(void)
                         I don’t get a warning when com...
#include <stdio.h>          a gets an undefined value

void foo(void)
                           I don’t get a warning when...
#include <stdio.h>                  a gets an undefined value

void foo(void)
                                  I don’t get...
#include <stdio.h>                                      a gets an undefined value

void foo(void)
                         ...
So what about this code snippet?
So what about this code snippet?
#include <stdio.h>

int b(void) { puts(“3”); return 3; }
int c(void) { puts(“4”); return ...
#include <stdio.h>

int b(void) { puts(“3”); return 3; }
int c(void) { puts(“4”); return 4; }

int main(void)
{
    int a ...
#include <stdio.h>

     int b(void) { puts(“3”); return 3; }
     int c(void) { puts(“4”); return 4; }

     int main(voi...
#include <stdio.h>

     int b(void) { puts(“3”); return 3; }
     int c(void) { puts(“4”); return 4; }

     int main(voi...
#include <stdio.h>

     int b(void) { puts(“3”); return 3; }
     int c(void) { puts(“4”); return 4; }

     int main(voi...
#include <stdio.h>

     int b(void) { puts(“3”); return 3; }
     int c(void) { puts(“4”); return 4; }

     int main(voi...
#include <stdio.h>

     int b(void) { puts(“3”); return 3; }
     int c(void) { puts(“4”); return 4; }

     int main(voi...
#include <stdio.h>

     int b(void) { puts(“3”); return 3; }
     int c(void) { puts(“4”); return 4; }

     int main(voi...
#include <stdio.h>

int b(void) { puts(“3”); return 3; }
int c(void) { puts(“4”); return 4; }

int main(void)
{
    int a ...
#include <stdio.h>

int b(void) { puts(“3”); return 3; }
int c(void) { puts(“4”); return 4; }

int main(void)
{
    int a ...
#include <stdio.h>

      int b(void) { puts(“3”); return 3; }
      int c(void) { puts(“4”); return 4; }

      int main(...
#include <stdio.h>

      int b(void) { puts(“3”); return 3; }
      int c(void) { puts(“4”); return 4; }

      int main(...
At this point I think he has just revealed a shallow
understanding of C programming, while she has
excelled in her answers...
So what is it that she seems to understand better than most?
So what is it that she seems to understand better than most?



               • Declaration and Definition
So what is it that she seems to understand better than most?



               • Declaration and Definition
               ...
So what is it that she seems to understand better than most?



               • Declaration and Definition
               ...
So what is it that she seems to understand better than most?



               • Declaration and Definition
               ...
So what is it that she seems to understand better than most?



               • Declaration and Definition
               ...
So what is it that she seems to understand better than most?



               • Declaration and Definition
               ...
We’d like to share some things about:




      Sequence points
      Different C standards
What do these code snippets print?
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);


2   int a=41; a++ & printf("%dn", a);
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);


2   int a=41; a++ & printf("%dn", a);


3   int...
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);


2   int a=41; a++ & printf("%dn", a);


3   int...
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);


2   int a=41; a++ & printf("%dn", a);


3   int...
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);            42

2   int a=41; a++ & printf("%dn", ...
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);            42

2   int a=41; a++ & printf("%dn", ...
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);            42

2   int a=41; a++ & printf("%dn", ...
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);            42

2   int a=41; a++ & printf("%dn", ...
What do these code snippets print?

1   int a=41; a++; printf("%dn", a);            42

2   int a=41; a++ & printf("%dn", ...
What do these code snippets print?

1    int a=41; a++; printf("%dn", a);            42

 2   int a=41; a++ & printf("%dn"...
Sequence Points
A sequence point is a point in the program's
execution sequence where all previous side-
effects shall hav...
Sequence Points - Rule 1
Between the previous and next sequence point an
object shall have its stored value modified at mo...
Sequence Points - Rule 2
Furthermore, the prior value shall be read only to
determine the value to be stored. (6.5)


    ...
Sequence Points

A lot of developers think C has many sequence points
Sequence Points

The reality is that C has very few sequence points.




This helps to maximize optimization opportunities...
/* K&R C */                         // C++ (C++98)

void say_it(a, s)                   #include <cstdio>
     int a;
    ...
Let’s get back to our two developers...
So what about this code snippet?
So what about this code snippet?
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%dn", sizeof...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%dn", sizeof...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%dn", sizeof...
#include <stdio.h>

       struct X { int a; char b; int c; };

       int main(void)
       {
           printf("%dn", si...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%dn", sizeof(int));
    printf("%dn"...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%zun", sizeof(int));
    printf("%zu...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%zun", sizeo...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%zun", sizeo...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%zun", sizeo...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%zun", sizeo...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%zun", sizeof(int));
    printf("%zu...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%zun", sizeof(int));
    printf("%zu...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%zun", sizeo...
#include <stdio.h>

      struct X { int a; char b; int c; };

      int main(void)
      {
          printf("%zun", sizeo...
#include <stdio.h>

                   struct X { int a; char b; int c; };

                   int main(void)
            ...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%zun", sizeof(int));
    printf("%zu...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%zun", sizeof(int));
    printf("%zu...
#include <stdio.h>

    struct X { int a; char b; int c; };

    int main(void)
    {
        printf("%zun", sizeof(int));...
#include <stdio.h>

    struct X { int a; char b; int c; };

    int main(void)
    {
        printf("%zun", sizeof(int));...
#include <stdio.h>

    struct X { int a; char b; int c; };

    int main(void)
    {
        printf("%zun", sizeof(int));...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%zun", sizeof(int));
    printf("%zu...
#include <stdio.h>

struct X { int a; char b; int c; };

int main(void)
{
    printf("%zun", sizeof(int));
    printf("%zu...
#include <stdio.h>

    struct X { int a; char b; int c; };

    int main(void)
    {
        printf("%zun", sizeof(int));...
#include <stdio.h>

    struct X { int a; char b; int c; };

    int main(void)
    {
        printf("%zun", sizeof(int));...
So what is it that she seems to understand better than most?
So what is it that she seems to understand better than most?




              • Some experience with 32-bit vs 64-bit iss...
So what is it that she seems to understand better than most?




              • Some experience with 32-bit vs 64-bit iss...
So what is it that she seems to understand better than most?




              • Some experience with 32-bit vs 64-bit iss...
So what is it that she seems to understand better than most?




              • Some experience with 32-bit vs 64-bit iss...
We’d like to share some things about:




            Memory model
            Optimization
            The spirit of C
Memory Model
static storage
An object whose identifier is declared with external or internal
linkage, or with the storage-...
Memory Model
automatic storage
An object whose identifier is declared with no linkage and
without the storage-class specif...
Memory Model
allocated storage
...storage allocated by calls to calloc, malloc, and realloc...
The lifetime of an allocate...
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
Deep C
You’ve finished this document.
Download and read it offline.
Upcoming SlideShare
Insecure coding in C (and C++)
Next
Upcoming SlideShare
Insecure coding in C (and C++)
Next
Download to read offline and view in fullscreen.

1521

Share

Deep C

Download to read offline

Programming is hard. Programming correct C and C++ is particularly hard. Indeed, both in C and certainly in C++, it is uncommon to see a screenful containing only well defined and conforming code.Why do professional programmers write code like this? Because most programmers do not have a deep understanding of the language they are using.While they sometimes know that certain things are undefined or unspecified, they often do not know why it is so. In these slides we will study small code snippets in C and C++, and use them to discuss the fundamental building blocks, limitations and underlying design philosophies of these wonderful but dangerous programming languages.

This content has a CC license. Feel free to use it for whatever you want. You may download the original PDF file from: http://www.pvv.org/~oma/DeepC_slides_oct2012.pdf

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Deep C

  1. Deep C (and C++) by Olve Maudal and Jon Jagger http://www.noaanews.noaa.gov/stories2005/images/rov-hercules-titanic.jpg Programming is hard. Programming correct C and C++ is particularly hard. Indeed, both in C and certainly in C++, it is uncommon to see a screenful containing only well defined and conforming code. Why do professional programmers write code like this? Because most programmers do not have a deep understanding of the language they are using. While they sometimes know that certain things are undefined or unspecified, they often do not know why it is so. In these slides we will study small code snippets in C and C++, and use them to discuss the fundamental building blocks, limitations and underlying design philosophies of these wonderful but dangerous programming languages. October 2011
  2. Suppose you are about to interview a candidate for a position as C programmer for various embedded platforms. As part of the interview you might want to check whether the candidate has a deep understanding of the programming language or not... here is a great code snippet to get the conversation started:
  3. Suppose you are about to interview a candidate for a position as C programmer for various embedded platforms. As part of the interview you might want to check whether the candidate has a deep understanding of the programming language or not... here is a great code snippet to get the conversation started: int main() { int a = 42; printf(“%dn”, a); }
  4. Suppose you are about to interview a candidate for a position as C programmer for various embedded platforms. As part of the interview you might want to check whether the candidate has a deep understanding of the programming language or not... here is a great code snippet to get the conversation started: int main() { int a = 42; printf(“%dn”, a); } What will happen if you try to compile, link and run this program?
  5. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); }
  6. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } One candidate might say:
  7. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } You must #include <stdio.h>, add One candidate might say: a return 0 and then it will compile and link. When executed it will print the value 42 on the screen.
  8. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } You must #include <stdio.h>, add One candidate might say: a return 0 and then it will compile and link. When executed it will print the value 42 on the screen. and there is nothing wrong with that answer...
  9. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); }
  10. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } But another candidate might use this as an opportunity to start demonstrating a deeper understanding. She might say things like:
  11. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } But another candidate might use this as an opportunity to start demonstrating a deeper understanding. She might say things like: You probably want to #include <stdio.h> which has an explicit declaration of printf(). The program will compile, link and run, and it will write the number 42 followed by a newline to the standard output stream.
  12. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and then she elaborates a bit by saying:
  13. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and then she elaborates A C++ compiler will refuse to compile this code as the language requires explicit declaration of all functions. a bit by saying:
  14. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and then she elaborates A C++ compiler will refuse to compile this code as the language requires explicit declaration of all functions. a bit by saying: However a proper C compiler will create an implicit declaration for the function printf(), compile this code into an object file.
  15. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and then she elaborates A C++ compiler will refuse to compile this code as the language requires explicit declaration of all functions. a bit by saying: However a proper C compiler will create an implicit declaration for the function printf(), compile this code into an object file. And when linked with a standard library, it will find a definition of printf()that accidentally will match the implicit declaration.
  16. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and then she elaborates A C++ compiler will refuse to compile this code as the language requires explicit declaration of all functions. a bit by saying: However a proper C compiler will create an implicit declaration for the function printf(), compile this code into an object file. And when linked with a standard library, it will find a definition of printf()that accidentally will match the implicit declaration. So the program above will actually compile, link and run.
  17. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and then she elaborates A C++ compiler will refuse to compile this code as the language requires explicit declaration of all functions. a bit by saying: However a proper C compiler will create an implicit declaration for the function printf(), compile this code into an object file. And when linked with a standard library, it will find a definition of printf()that accidentally will match the implicit declaration. So the program above will actually compile, link and run. You might get a warning though.
  18. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and while she is on the roll, she might continue with:
  19. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and while she is on the roll, she might continue with: If this is C99, the exit value is defined to indicate success to the runtime environment, just like in C++98, but for older versions of C, like ANSI C and K&R, the exit value from this program will be some undefined garbage value.
  20. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and while she is on the roll, she might continue with: If this is C99, the exit value is defined to indicate success to the runtime environment, just like in C++98, but for older versions of C, like ANSI C and K&R, the exit value from this program will be some undefined garbage value. But since return values are often passed in a register I would not be surprised if the garbage value happens to be 3... since printf() will return 3, the number of characters written to standard out.
  21. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and while she is on the roll, she might continue with:
  22. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); } and while she is on the roll, she might continue with: And talking about C standards... if you want to show that you care about C programming, you should use int main(void) as your entry point - since the standard says so. Using void to indicate no parameters is essential for declarations in C, eg a declaration ‘int f();’, says there is a function f that takes any number of arguments. While you probably meant to say ‘int f(void);’. Being explicit by using void also for function definitions does not hurt.
  23. What will happen if you try to compile, link and run this program? int main() { int a = 42; printf(“%dn”, a); }
  24. What will happen if you try to compile, link and run this program? int main(void) { int a = 42; printf(“%dn”, a); }
  25. What will happen if you try to compile, link and run this program? int main(void) { int a = 42; printf(“%dn”, a); } and to really show off... Also, if you allow me to be a bit pedantic... the program is not really compliant, as the standard says that the source code must end with a newline.
  26. What will happen if you try to compile, link and run this program? int main(void) { int a = 42; printf(“%dn”, a); }
  27. What will happen if you try to compile, link and run this program? int main(void) { int a = 42; printf(“%dn”, a); }
  28. What will happen if you try to compile, link and run this program? int main(void) { int a = 42; printf(“%dn”, a); } ah, remember to include an explicit declaration of printf() as well
  29. What will happen if you try to compile, link and run this program? int main(void) { int a = 42; printf(“%dn”, a); }
  30. What will happen if you try to compile, link and run this program? int main(void) { int a = 42; printf(“%dn”, a); }
  31. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); }
  32. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } now, this is a darn cute little C program! Isn’t it?
  33. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine:
  34. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c
  35. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc foo.o
  36. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc foo.o $ ./a.out
  37. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc foo.o $ ./a.out 42
  38. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc foo.o $ ./a.out 42 $ echo $?
  39. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc foo.o $ ./a.out 42 $ echo $? 3
  40. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc -std=c99 -c foo.c $ cc foo.o $ ./a.out 42 $ echo $? 3
  41. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc -std=c99 -c foo.c $ cc foo.o $ cc foo.o $ ./a.out 42 $ echo $? 3
  42. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc -std=c99 -c foo.c $ cc foo.o $ cc foo.o $ ./a.out $ ./a.out 42 $ echo $? 3
  43. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc -std=c99 -c foo.c $ cc foo.o $ cc foo.o $ ./a.out $ ./a.out 42 42 $ echo $? 3
  44. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc -std=c99 -c foo.c $ cc foo.o $ cc foo.o $ ./a.out $ ./a.out 42 42 $ echo $? $ echo $? 3
  45. What will happen if you try to compile, link and run this program? #include <stdio.h> int main(void) { int a = 42; printf(“%dn”, a); } and here is what I get when compiling, linking and running the above program on my machine: $ cc -std=c89 -c foo.c $ cc -std=c99 -c foo.c $ cc foo.o $ cc foo.o $ ./a.out $ ./a.out 42 42 $ echo $? $ echo $? 3 0
  46. Is there any difference between these two candidates?
  47. Is there any difference between these two candidates? Not much, yet, but I really like her answers so far.
  48. Now suppose they are not really candidates. Perhaps they are stereotypes for engineers working in your organization?
  49. Now suppose they are not really candidates. Perhaps they are stereotypes for engineers working in your organization?
  50. Now suppose they are not really candidates. Perhaps they are stereotypes for engineers working in your organization? Would it be useful if most of your colleagues have a deep understanding of the programming language they are using?
  51. Let’s find out how deep their knowledge of C and C++ is...
  52. Let’s find out how deep their knowledge of C and C++ is...
  53. #include <stdio.h> void foo(void) { int a = 3; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  54. #include <stdio.h> it will print 4, then 4, then 4 void foo(void) { int a = 3; ++a; printf("%dn", a); } int main(void) { foo(); it will print 4, then 4, then 4 foo(); foo(); }
  55. #include <stdio.h> void foo(void) { int a = 3; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  56. #include <stdio.h> void foo(void) { static int a = 3; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  57. #include <stdio.h> it will print 4, then 5, then 6 void foo(void) { static int a = 3; ++a; printf("%dn", a); } int main(void) { foo(); it will print 4, then 5, then 6 foo(); foo(); }
  58. #include <stdio.h> void foo(void) { static int a = 3; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  59. #include <stdio.h> void foo(void) { static int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  60. #include <stdio.h> void foo(void) { static int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  61. #include <stdio.h> void foo(void) { static int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  62. #include <stdio.h> eh, is it undefined? do you get garbage values? void foo(void) { static int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  63. #include <stdio.h> eh, is it undefined? do you get garbage values? void foo(void) No, you get 1, then 2, then 3 { static int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  64. #include <stdio.h> eh, is it undefined? do you get garbage values? void foo(void) No, you get 1, then 2, then 3 { static int a; ++a; ok, I see... why? printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  65. #include <stdio.h> eh, is it undefined? do you get garbage values? void foo(void) No, you get 1, then 2, then 3 { static int a; ++a; ok, I see... why? printf("%dn", a); } because static variables are set to 0 int main(void) { foo(); foo(); foo(); }
  66. #include <stdio.h> eh, is it undefined? do you get garbage values? void foo(void) No, you get 1, then 2, then 3 { static int a; ++a; ok, I see... why? printf("%dn", a); } because static variables are set to 0 int main(void) { foo(); foo(); foo(); }
  67. #include <stdio.h> eh, is it undefined? do you get garbage values? void foo(void) No, you get 1, then 2, then 3 { static int a; ++a; ok, I see... why? printf("%dn", a); } because static variables are set to 0 int main(void) { foo(); foo(); the standard says that static variables are initialized foo(); to 0, so this should print 1, then 2, then 3 }
  68. #include <stdio.h> void foo(void) { static int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  69. #include <stdio.h> void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  70. #include <stdio.h> void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  71. #include <stdio.h> void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  72. Now you get 1, then 1, then 1 #include <stdio.h> void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  73. Now you get 1, then 1, then 1 #include <stdio.h> Ehm, why do you think that will happen? void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  74. Now you get 1, then 1, then 1 #include <stdio.h> Ehm, why do you think that will happen? void foo(void) { Because you said they where initialized to 0 int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  75. Now you get 1, then 1, then 1 #include <stdio.h> Ehm, why do you think that will happen? void foo(void) { Because you said they where initialized to 0 int a; ++a; But this is not a static variable printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  76. Now you get 1, then 1, then 1 #include <stdio.h> Ehm, why do you think that will happen? void foo(void) { Because you said they where initialized to 0 int a; ++a; But this is not a static variable printf("%dn", a); } ah, then you get three garbage values int main(void) { foo(); foo(); foo(); }
  77. Now you get 1, then 1, then 1 #include <stdio.h> Ehm, why do you think that will happen? void foo(void) { Because you said they where initialized to 0 int a; ++a; But this is not a static variable printf("%dn", a); } ah, then you get three garbage values int main(void) { foo(); foo(); foo(); }
  78. Now you get 1, then 1, then 1 #include <stdio.h> Ehm, why do you think that will happen? void foo(void) { Because you said they where initialized to 0 int a; ++a; But this is not a static variable printf("%dn", a); } ah, then you get three garbage values int main(void) the value of a will be undefinded, so in theory you { get three garbage values. In practice however, since foo(); auto variables are often allocated on an execution foo(); stack, a might get the same memory location each foo(); time and you might get three consecutive values... if } you compile without optimization.
  79. Now you get 1, then 1, then 1 #include <stdio.h> Ehm, why do you think that will happen? void foo(void) { Because you said they where initialized to 0 int a; ++a; But this is not a static variable printf("%dn", a); } ah, then you get three garbage values int main(void) the value of a will be undefinded, so in theory you { get three garbage values. In practice however, since foo(); auto variables are often allocated on an execution foo(); stack, a might get the same memory location each foo(); time and you might get three consecutive values... if } you compile without optimization. on my machine I actually get, 1, then 2, then 3
  80. Now you get 1, then 1, then 1 #include <stdio.h> Ehm, why do you think that will happen? void foo(void) { Because you said they where initialized to 0 int a; ++a; But this is not a static variable printf("%dn", a); } ah, then you get three garbage values int main(void) the value of a will be undefinded, so in theory you { get three garbage values. In practice however, since foo(); auto variables are often allocated on an execution foo(); stack, a might get the same memory location each foo(); time and you might get three consecutive values... if } you compile without optimization. on my machine I actually get, 1, then 2, then 3 I am not surprised... if you compile in debug mode the runtime might try to be helpful and memset your stack memory to 0
  81. #include <stdio.h> void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  82. #include <stdio.h> Why do you think static variables are set to 0, while auto variables are not initialized? void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  83. #include <stdio.h> Why do you think static variables are set to 0, while auto variables are not initialized? void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  84. #include <stdio.h> Why do you think static variables are set to 0, while auto variables are not initialized? void foo(void) { int a; eh? ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  85. #include <stdio.h> Why do you think static variables are set to 0, while auto variables are not initialized? void foo(void) { int a; eh? ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  86. #include <stdio.h> Why do you think static variables are set to 0, while auto variables are not initialized? void foo(void) { int a; eh? ++a; printf("%dn", a); } The cost of setting auto variables to 0 would increase the cost of function calls. C has a very int main(void) strong focus on execution speed. { foo(); foo(); foo(); }
  87. #include <stdio.h> Why do you think static variables are set to 0, while auto variables are not initialized? void foo(void) { int a; eh? ++a; printf("%dn", a); } The cost of setting auto variables to 0 would increase the cost of function calls. C has a very int main(void) strong focus on execution speed. { foo(); foo(); Memsetting the global data segment to 0 foo(); however, is a one time cost that happens at } start up, and that might be the reason why it is so in C.
  88. #include <stdio.h> Why do you think static variables are set to 0, while auto variables are not initialized? void foo(void) { int a; eh? ++a; printf("%dn", a); } The cost of setting auto variables to 0 would increase the cost of function calls. C has a very int main(void) strong focus on execution speed. { foo(); foo(); Memsetting the global data segment to 0 foo(); however, is a one time cost that happens at } start up, and that might be the reason why it is so in C. And to be precise, in C++ however, static variables are not set to 0, they are set to their default values... which for native types means 0.
  89. #include <stdio.h> void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  90. #include <stdio.h> void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  91. #include <stdio.h> void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  92. #include <stdio.h> static int a; void foo(void) { int a; ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  93. #include <stdio.h> static int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  94. #include <stdio.h> static int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  95. #include <stdio.h> static int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  96. #include <stdio.h> static int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  97. 1, 2, 3 #include <stdio.h> static int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  98. 1, 2, 3 #include <stdio.h> ok, why? static int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  99. 1, 2, 3 #include <stdio.h> ok, why? static int a; because a is static, and therefore initialized to 0 void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  100. 1, 2, 3 #include <stdio.h> ok, why? static int a; because a is static, and therefore initialized to 0 void foo(void) { I agree... ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  101. 1, 2, 3 #include <stdio.h> ok, why? static int a; because a is static, and therefore initialized to 0 void foo(void) { I agree... ++a; printf("%dn", a); cool! } int main(void) { foo(); foo(); foo(); }
  102. #include <stdio.h> static int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  103. #include <stdio.h> int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  104. #include <stdio.h> int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  105. #include <stdio.h> int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  106. garbage, garbage, garbage #include <stdio.h> int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  107. garbage, garbage, garbage #include <stdio.h> why do you think that? int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  108. garbage, garbage, garbage #include <stdio.h> why do you think that? int a; oh, is it still initialized to 0? void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  109. garbage, garbage, garbage #include <stdio.h> why do you think that? int a; oh, is it still initialized to 0? void foo(void) { yes ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  110. garbage, garbage, garbage #include <stdio.h> why do you think that? int a; oh, is it still initialized to 0? void foo(void) { yes ++a; printf("%dn", a); maybe it will print 1, 2, 3? } int main(void) { foo(); foo(); foo(); }
  111. garbage, garbage, garbage #include <stdio.h> why do you think that? int a; oh, is it still initialized to 0? void foo(void) { yes ++a; printf("%dn", a); maybe it will print 1, 2, 3? } yes int main(void) { foo(); foo(); foo(); }
  112. garbage, garbage, garbage #include <stdio.h> why do you think that? int a; oh, is it still initialized to 0? void foo(void) { yes ++a; printf("%dn", a); maybe it will print 1, 2, 3? } yes int main(void) { do you know the difference between this code foo(); snippet and the previous code snippet (with static foo(); before int a)? foo(); }
  113. garbage, garbage, garbage #include <stdio.h> why do you think that? int a; oh, is it still initialized to 0? void foo(void) { yes ++a; printf("%dn", a); maybe it will print 1, 2, 3? } yes int main(void) { do you know the difference between this code foo(); snippet and the previous code snippet (with static foo(); before int a)? foo(); } not really, or wait a minute, it has do with private variables and public variables.
  114. garbage, garbage, garbage #include <stdio.h> why do you think that? int a; oh, is it still initialized to 0? void foo(void) { yes ++a; printf("%dn", a); maybe it will print 1, 2, 3? } yes int main(void) { do you know the difference between this code foo(); snippet and the previous code snippet (with static foo(); before int a)? foo(); } not really, or wait a minute, it has do with private variables and public variables. yeah, something like that...
  115. #include <stdio.h> int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  116. #include <stdio.h> int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  117. it will print 1, 2, 3, the variable is still statically #include <stdio.h> allocated and it will be set to 0 int a; void foo(void) { ++a; printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  118. it will print 1, 2, 3, the variable is still statically #include <stdio.h> allocated and it will be set to 0 int a; void foo(void) do you know the difference between this { code snippet and the previous code ++a; snippet (with static before int a)? printf("%dn", a); } int main(void) { foo(); foo(); foo(); }
  119. it will print 1, 2, 3, the variable is still statically #include <stdio.h> allocated and it will be set to 0 int a; void foo(void) do you know the difference between this { code snippet and the previous code ++a; snippet (with static before int a)? printf("%dn", a); } int main(void) { sure, it has to do with linker visibility. Here the variable is foo(); accessible from other compilation units, ie the linker can let foo(); another object file access this variable. If you add static in foo(); front, then the variable is local to this compilation unit and } not visible through the linker.
  120. I am now going to show you something cool!
  121. I am now going to show you something cool! #include <stdio.h> void foo(void) { int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  122. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out void foo(void) { int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  123. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  124. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Can you explain this behaviour? int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  125. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Can you explain this behaviour? int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  126. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Can you explain this behaviour? int a; printf("%dn", a); } eh? void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  127. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Can you explain this behaviour? int a; printf("%dn", a); } eh? void bar(void) Perhaps this compiler has a pool of { named variables that it reuses. Eg int a = 42; variable a was used and released in } bar(), then when foo() needs an integer names a it will get the int main(void) variable will get the same memory { location. If you rename the variable bar(); in bar() to, say b, then I don’t think foo(); you will get 42. }
  128. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Can you explain this behaviour? int a; printf("%dn", a); } eh? void bar(void) Perhaps this compiler has a pool of { named variables that it reuses. Eg int a = 42; variable a was used and released in } bar(), then when foo() needs an integer names a it will get the int main(void) variable will get the same memory { location. If you rename the variable bar(); in bar() to, say b, then I don’t think foo(); you will get 42. } Yeah, sure...
  129. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  130. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  131. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Nice! I love it! int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  132. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Nice! I love it! int a; printf("%dn", a); You now want me to explain about } execution stack or activation frames? void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  133. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Nice! I love it! int a; printf("%dn", a); You now want me to explain about } execution stack or activation frames? void bar(void) I guess you have already demonstrated { that you understand it. But what do you int a = 42; think might happen if we optimize this } code or use another compiler? int main(void) { bar(); foo(); }
  134. I am now going to show you something cool! #include <stdio.h> $ cc foo.c && ./a.out 42 void foo(void) { Nice! I love it! int a; printf("%dn", a); You now want me to explain about } execution stack or activation frames? void bar(void) I guess you have already demonstrated { that you understand it. But what do you int a = 42; think might happen if we optimize this } code or use another compiler? int main(void) { A lot of things might happen when the optimizer kicks in. In bar(); this case I would guess that the call to bar() can be skipped as foo(); it does not have any side effects. Also, I would not be surprised } if the foo() is inlined in main(), ie no function call. (But since foo () has linker visibility the object code for the function must still be created just in case another object file wants to link with the function). Anyway, I suspect the value printed will be something else if you optimize the code.
  135. #include <stdio.h> $ cc -O foo.c && ./a.out 1606415608 void foo(void) { int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  136. #include <stdio.h> $ cc -O foo.c && ./a.out 1606415608 void foo(void) { int a; printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  137. #include <stdio.h> $ cc -O foo.c && ./a.out 1606415608 void foo(void) { int a; Garbage! printf("%dn", a); } void bar(void) { int a = 42; } int main(void) { bar(); foo(); }
  138. So what about this code snippet?
  139. So what about this code snippet? #include <stdio.h> void foo(void) { int a = 41; a = a++; printf("%dn", a); } int main(void) { foo(); }
  140. #include <stdio.h> void foo(void) { int a = 41; a = a++; printf("%dn", a); } int main(void) { foo(); }
  141. #include <stdio.h> I would never write code like that. void foo(void) { int a = 41; a = a++; printf("%dn", a); } int main(void) { foo(); }
  142. #include <stdio.h> I would never write code like that. void foo(void) That’s nice to hear! { int a = 41; a = a++; printf("%dn", a); } int main(void) { foo(); }
  143. #include <stdio.h> I would never write code like that. void foo(void) That’s nice to hear! { int a = 41; a = a++; But I think the answer is 42 printf("%dn", a); } int main(void) { foo(); }
  144. #include <stdio.h> I would never write code like that. void foo(void) That’s nice to hear! { int a = 41; a = a++; But I think the answer is 42 printf("%dn", a); } Why do you think that? int main(void) { foo(); }
  145. #include <stdio.h> I would never write code like that. void foo(void) That’s nice to hear! { int a = 41; a = a++; But I think the answer is 42 printf("%dn", a); } Why do you think that? int main(void) Because what else can it be? { foo(); }
  146. #include <stdio.h> I would never write code like that. void foo(void) That’s nice to hear! { int a = 41; a = a++; But I think the answer is 42 printf("%dn", a); } Why do you think that? int main(void) Because what else can it be? { foo(); Indeed, 42 is exactly what I get when I } run this on my machine
  147. #include <stdio.h> I would never write code like that. void foo(void) That’s nice to hear! { int a = 41; a = a++; But I think the answer is 42 printf("%dn", a); } Why do you think that? int main(void) Because what else can it be? { foo(); Indeed, 42 is exactly what I get when I } run this on my machine hey, you see!
  148. #include <stdio.h> I would never write code like that. void foo(void) That’s nice to hear! { int a = 41; a = a++; But I think the answer is 42 printf("%dn", a); } Why do you think that? int main(void) Because what else can it be? { foo(); Indeed, 42 is exactly what I get when I } run this on my machine hey, you see! But the code is actually undefined.
  149. #include <stdio.h> I would never write code like that. void foo(void) That’s nice to hear! { int a = 41; a = a++; But I think the answer is 42 printf("%dn", a); } Why do you think that? int main(void) Because what else can it be? { foo(); Indeed, 42 is exactly what I get when I } run this on my machine hey, you see! But the code is actually undefined. Yeah, I told you - I never write code like that
  150. #include <stdio.h> void foo(void) { int a = 41; a = a++; printf("%dn", a); } int main(void) { foo(); }
  151. #include <stdio.h> void foo(void) { int a = 41; a = a++; printf("%dn", a); } int main(void) { foo(); }
  152. #include <stdio.h> a gets an undefined value void foo(void) { int a = 41; a = a++; printf("%dn", a); } int main(void) { foo(); }
  153. #include <stdio.h> a gets an undefined value void foo(void) I don’t get a warning when compiling it, { and I do get 42 int a = 41; a = a++; printf("%dn", a); } int main(void) { foo(); }
  154. #include <stdio.h> a gets an undefined value void foo(void) I don’t get a warning when compiling it, { and I do get 42 int a = 41; a = a++; printf("%dn", a); Then you must increase the warning level, } the value of a is certainly undefined after the assignment and increment because you int main(void) violate one of the fundamental rules in C { (and C++). The rules for sequencing says foo(); that you can only update a variable once } between sequence points. Here you try to update it two times, and this causes a to become undefined.
  155. #include <stdio.h> a gets an undefined value void foo(void) I don’t get a warning when compiling it, { and I do get 42 int a = 41; a = a++; printf("%dn", a); Then you must increase the warning level, } the value of a is certainly undefined after the assignment and increment because you int main(void) violate one of the fundamental rules in C { (and C++). The rules for sequencing says foo(); that you can only update a variable once } between sequence points. Here you try to update it two times, and this causes a to become undefined. So you say a can be whatever? But I do get 42
  156. #include <stdio.h> a gets an undefined value void foo(void) I don’t get a warning when compiling it, { and I do get 42 int a = 41; a = a++; printf("%dn", a); Then you must increase the warning level, } the value of a is certainly undefined after the assignment and increment because you int main(void) violate one of the fundamental rules in C { (and C++). The rules for sequencing says foo(); that you can only update a variable once } between sequence points. Here you try to update it two times, and this causes a to become undefined. So you say a can be whatever? But I do get 42 Indeed! a can be 42, 41, 43, 0, 1099, or whatever... I am not surprised that your machine gives you 42... what else can it be here? Or perhaps the compiler choose 42 whenever a value is undefined ;-)
  157. So what about this code snippet?
  158. So what about this code snippet? #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); }
  159. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); }
  160. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); } Easy, it prints 3, 4 and then 7
  161. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); } Easy, it prints 3, 4 and then 7 Actually, this could also be 4, 3 and then 7
  162. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); } Easy, it prints 3, 4 and then 7 Actually, this could also be 4, 3 and then 7 Huh? Is the evaluation order undefined?
  163. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); } Easy, it prints 3, 4 and then 7 Actually, this could also be 4, 3 and then 7 Huh? Is the evaluation order undefined? It is not really undefined, it is unspecified
  164. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); } Easy, it prints 3, 4 and then 7 Actually, this could also be 4, 3 and then 7 Huh? Is the evaluation order undefined? It is not really undefined, it is unspecified Well, whatever. Lousy compilers. I think it should give us a warning?
  165. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); } Easy, it prints 3, 4 and then 7 Actually, this could also be 4, 3 and then 7 Huh? Is the evaluation order undefined? It is not really undefined, it is unspecified Well, whatever. Lousy compilers. I think it should give us a warning? A warning about what?
  166. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); }
  167. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); }
  168. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); } The evaluation order of most expressions in C and C++ are unspecified, the compiler can choose to evaluate them in the order that is most optimal for the target platform. This has to do with sequencing again. The code is conforming. This code will either print 3, 4, 7 or 4, 3, 7, depending on the compiler.
  169. #include <stdio.h> int b(void) { puts(“3”); return 3; } int c(void) { puts(“4”); return 4; } int main(void) { int a = b() + c(); printf(“%dn”, a); } The evaluation order of most expressions in C and C++ are unspecified, the compiler can choose to evaluate them in the order that is most optimal for the target platform. This has to do with sequencing again. The code is conforming. This code will either print 3, 4, 7 or 4, 3, 7, depending on the compiler. Life would be so easy if more of my colleagues knew stuff like she does
  170. At this point I think he has just revealed a shallow understanding of C programming, while she has excelled in her answers so far.
  171. So what is it that she seems to understand better than most?
  172. So what is it that she seems to understand better than most? • Declaration and Definition
  173. So what is it that she seems to understand better than most? • Declaration and Definition • Calling conventions and activation frames
  174. So what is it that she seems to understand better than most? • Declaration and Definition • Calling conventions and activation frames • Sequence points
  175. So what is it that she seems to understand better than most? • Declaration and Definition • Calling conventions and activation frames • Sequence points • Memory model
  176. So what is it that she seems to understand better than most? • Declaration and Definition • Calling conventions and activation frames • Sequence points • Memory model • Optimization
  177. So what is it that she seems to understand better than most? • Declaration and Definition • Calling conventions and activation frames • Sequence points • Memory model • Optimization • Knowledge of different C standards
  178. We’d like to share some things about: Sequence points Different C standards
  179. What do these code snippets print?
  180. What do these code snippets print? 1 int a=41; a++; printf("%dn", a);
  181. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 2 int a=41; a++ & printf("%dn", a);
  182. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 2 int a=41; a++ & printf("%dn", a); 3 int a=41; a++ && printf("%dn", a);
  183. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 2 int a=41; a++ & printf("%dn", a); 3 int a=41; a++ && printf("%dn", a); 4 int a=41; if (a++ < 42) printf("%dn", a);
  184. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 2 int a=41; a++ & printf("%dn", a); 3 int a=41; a++ && printf("%dn", a); 4 int a=41; if (a++ < 42) printf("%dn", a); 5 int a=41; a = a++; printf("%dn", a);
  185. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 42 2 int a=41; a++ & printf("%dn", a); 3 int a=41; a++ && printf("%dn", a); 4 int a=41; if (a++ < 42) printf("%dn", a); 5 int a=41; a = a++; printf("%dn", a);
  186. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 42 2 int a=41; a++ & printf("%dn", a); undefined 3 int a=41; a++ && printf("%dn", a); 4 int a=41; if (a++ < 42) printf("%dn", a); 5 int a=41; a = a++; printf("%dn", a);
  187. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 42 2 int a=41; a++ & printf("%dn", a); undefined 3 int a=41; a++ && printf("%dn", a); 42 4 int a=41; if (a++ < 42) printf("%dn", a); 5 int a=41; a = a++; printf("%dn", a);
  188. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 42 2 int a=41; a++ & printf("%dn", a); undefined 3 int a=41; a++ && printf("%dn", a); 42 4 int a=41; if (a++ < 42) printf("%dn", a); 42 5 int a=41; a = a++; printf("%dn", a);
  189. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 42 2 int a=41; a++ & printf("%dn", a); undefined 3 int a=41; a++ && printf("%dn", a); 42 4 int a=41; if (a++ < 42) printf("%dn", a); 42 5 int a=41; a = a++; printf("%dn", a); undefined
  190. What do these code snippets print? 1 int a=41; a++; printf("%dn", a); 42 2 int a=41; a++ & printf("%dn", a); undefined 3 int a=41; a++ && printf("%dn", a); 42 4 int a=41; if (a++ < 42) printf("%dn", a); 42 5 int a=41; a = a++; printf("%dn", a); undefined When exactly do side-effects take place in C and C++?
  191. Sequence Points A sequence point is a point in the program's execution sequence where all previous side- effects shall have taken place and where all subsequent side-effects shall not have taken place (5.1.2.3)
  192. Sequence Points - Rule 1 Between the previous and next sequence point an object shall have its stored value modified at most once by the evaluation of an expression. (6.5) a = a++ this is undefined!
  193. Sequence Points - Rule 2 Furthermore, the prior value shall be read only to determine the value to be stored. (6.5) a + a++ this is undefined!!
  194. Sequence Points A lot of developers think C has many sequence points
  195. Sequence Points The reality is that C has very few sequence points. This helps to maximize optimization opportunities for the compiler.
  196. /* K&R C */ // C++ (C++98) void say_it(a, s) #include <cstdio> int a; char s[]; struct X { { int a; printf("%s %dn", s, a); const char * s; } explicit X(const char * s, int a = 42) : a(a), s(s) {} main() void say_it() const { { std::printf("%s %dn", s, a); int a = 42; } puts("Welcome to classic C"); }; say_it(a, "the answer is"); } int main() { X("the answer is").say_it(); /* C89 */ } void say_it(int a, char * s) // C99 { printf("%s %dn", s, a); struct X } { int a; main() char * s; { }; int a = 42; puts("Welcome to C89"); int main(void) say_it(a, "the answer is"); { } puts("Welcome to C99"); struct X x = { .s = "the answer is", .a = 42 }; printf("%s %dn", x.s, x.a); }
  197. Let’s get back to our two developers...
  198. So what about this code snippet?
  199. So what about this code snippet? #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); }
  200. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); }
  201. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } It will print 4, 1 and 12
  202. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } It will print 4, 1 and 12 Indeed, it is exactly what I get on my machine
  203. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } It will print 4, 1 and 12 Indeed, it is exactly what I get on my machine Well of course, because sizeof returns the number of bytes. And in C int is 32 bits or 4 bytes, char is one byte and when the the size of structs are always rounded up to multiples of 4
  204. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } It will print 4, 1 and 12 Indeed, it is exactly what I get on my machine Well of course, because sizeof returns the number of bytes. And in C int is 32 bits or 4 bytes, char is one byte and when the the size of structs are always rounded up to multiples of 4 ok
  205. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } It will print 4, 1 and 12 Indeed, it is exactly what I get on my machine Well of course, because sizeof returns the number of bytes. And in C int is 32 bits or 4 bytes, char is one byte and when the the size of structs are always rounded up to multiples of 4 ok do you want another ice cream?
  206. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); }
  207. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); }
  208. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } Hmm... first of all, let’s fix the code. The return type of sizeof is size_t which is not the same as int, so %d is a poor specifier to use in the format string for printf here
  209. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } Hmm... first of all, let’s fix the code. The return type of sizeof is size_t which is not the same as int, so %d is a poor specifier to use in the format string for printf here ok, what should specifier should we use?
  210. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } Hmm... first of all, let’s fix the code. The return type of sizeof is size_t which is not the same as int, so %d is a poor specifier to use in the format string for printf here ok, what should specifier should we use? Thats a bit tricky. size_t is an unsigned integer type, but on say 32-bit machines it is usually an unsigned int and on 64-bit machines it is usually an unsigned long. In C99 however, they introduced a new specifier for printing size_t values, so %zu might be an option.
  211. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); } Hmm... first of all, let’s fix the code. The return type of sizeof is size_t which is not the same as int, so %d is a poor specifier to use in the format string for printf here ok, what should specifier should we use? Thats a bit tricky. size_t is an unsigned integer type, but on say 32-bit machines it is usually an unsigned int and on 64-bit machines it is usually an unsigned long. In C99 however, they introduced a new specifier for printing size_t values, so %zu might be an option. ok, let’s fix the printf issue, and then you can try to answer the question
  212. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%dn", sizeof(int)); printf("%dn", sizeof(char)); printf("%dn", sizeof(struct X)); }
  213. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); }
  214. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } Now it all depends on the platform and the compile time options provided. The only thing we know for sure is that sizeof char is 1. Do you assume a 64-bit machine?
  215. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } Now it all depends on the platform and the compile time options provided. The only thing we know for sure is that sizeof char is 1. Do you assume a 64-bit machine? Yes, I have a 64-bit machine running in 32-bit compatibility mode.
  216. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } Now it all depends on the platform and the compile time options provided. The only thing we know for sure is that sizeof char is 1. Do you assume a 64-bit machine? Yes, I have a 64-bit machine running in 32-bit compatibility mode. Then I would like to guess that this prints 4, 1, 12 due to word alignment
  217. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } Now it all depends on the platform and the compile time options provided. The only thing we know for sure is that sizeof char is 1. Do you assume a 64-bit machine? Yes, I have a 64-bit machine running in 32-bit compatibility mode. Then I would like to guess that this prints 4, 1, 12 due to word alignment But that of course also depends also on compilation flags. It could be 4, 1, 9 if you ask the compiler to pack the structs, eg -fpack-struct in gcc.
  218. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); }
  219. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } 4, 1, 12 is indeed what I get on my machine. Why 12?
  220. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } 4, 1, 12 is indeed what I get on my machine. Why 12? It is very expensive to work on subword data types, so the compiler will optimize the code by making sure that c is on a word boundary by adding some padding. Also elements in an array of struct X will now align on word-boundaries.
  221. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } 4, 1, 12 is indeed what I get on my machine. Why 12? It is very expensive to work on subword data types, so the compiler will optimize the code by making sure that c is on a word boundary by adding some padding. Also elements in an array of struct X will now align on word-boundaries. Why is it expensive to work on values that are not aligned?
  222. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } 4, 1, 12 is indeed what I get on my machine. Why 12? It is very expensive to work on subword data types, so the compiler will optimize the code by making sure that c is on a word boundary by adding some padding. Also elements in an array of struct X will now align on word-boundaries. Why is it expensive to work on values that are not aligned? The instruction set of most processors are optimized for moving a word of data between memory and CPU. Suppose you want to change a value crossing a word boundary, you would need to read two words, mask out the value, change the value, mask and write back two words. Perhaps 10 times slower. Remember, C is focused on execution speed.
  223. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); }
  224. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } so what if I add a char d to the struct?
  225. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } so what if I add a char d to the struct? If you add it to the end of the struct, my guess is that the size of the struct becomes 16 on your machine. This is first of all because 13 would be a not so efficient size, what if you have an array of struct X objects? But if you add it just after char b, then 12 is a more plausible answer.
  226. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } so what if I add a char d to the struct? If you add it to the end of the struct, my guess is that the size of the struct becomes 16 on your machine. This is first of all because 13 would be a not so efficient size, what if you have an array of struct X objects? But if you add it just after char b, then 12 is a more plausible answer. So why doesn’t the compiler reorder the members in the structure to optimize memory usage, and execution speed?
  227. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } so what if I add a char d to the struct? If you add it to the end of the struct, my guess is that the size of the struct becomes 16 on your machine. This is first of all because 13 would be a not so efficient size, what if you have an array of struct X objects? But if you add it just after char b, then 12 is a more plausible answer. So why doesn’t the compiler reorder the members in the structure to optimize memory usage, and execution speed? Some languages actually do that, but C and C++ don’t.
  228. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); }
  229. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } so what if I add a char * d to the end of the struct?
  230. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } so what if I add a char * d to the end of the struct? You said your runtime was 64-bit, so a pointer is probably 8 bytes... Maybe the struct becomes 20? But perhaps the 64-bit pointer also needs alignment for efficiency? Maybe this code will print 4,1,24?
  231. #include <stdio.h> struct X { int a; char b; int c; }; int main(void) { printf("%zun", sizeof(int)); printf("%zun", sizeof(char)); printf("%zun", sizeof(struct X)); } so what if I add a char * d to the end of the struct? You said your runtime was 64-bit, so a pointer is probably 8 bytes... Maybe the struct becomes 20? But perhaps the 64-bit pointer also needs alignment for efficiency? Maybe this code will print 4,1,24? Nice answer! It does not matter what I actually get on my machine. I like your argument and your insight.
  232. So what is it that she seems to understand better than most?
  233. So what is it that she seems to understand better than most? • Some experience with 32-bit vs 64-bit issues
  234. So what is it that she seems to understand better than most? • Some experience with 32-bit vs 64-bit issues • Memory alignment
  235. So what is it that she seems to understand better than most? • Some experience with 32-bit vs 64-bit issues • Memory alignment • CPU and memory optimization
  236. So what is it that she seems to understand better than most? • Some experience with 32-bit vs 64-bit issues • Memory alignment • CPU and memory optimization • Spirit of C
  237. We’d like to share some things about: Memory model Optimization The spirit of C
  238. Memory Model static storage An object whose identifier is declared with external or internal linkage, or with the storage-class specifier static has static storage duration. It’s lifetime is the entire execution of the program... (6.2.4) int * immortal(void) { static int storage = 42; return &storage; }
  239. Memory Model automatic storage An object whose identifier is declared with no linkage and without the storage-class specifier static has automatic storage duration. ... It’s lifetime extends from entry into the block with which it is associated until execution of that block ends in any way. (6.2.4) int * zombie(void) { auto int storage = 42; return &storage; }
  240. Memory Model allocated storage ...storage allocated by calls to calloc, malloc, and realloc... The lifetime of an allocated object extends from the allocation to the dealloction. (7.20.3) int * finite(void) { int * ptr = malloc(sizeof *ptr); *ptr = 42; return ptr; }
  • w1resh4rk

    Sep. 14, 2021
  • NirLevy23

    Sep. 13, 2021
  • picosleep

    Aug. 18, 2021
  • NhatDuyTran

    Apr. 5, 2021
  • EmersonBGrisi

    Mar. 19, 2021
  • ThngHong28

    Feb. 4, 2021
  • RoshanJames9

    Jan. 26, 2021
  • NickKite2

    Nov. 20, 2020
  • XuyenTran6

    Nov. 13, 2020
  • YahyaAhmed29

    Nov. 6, 2020
  • KuldeepSavaliya

    Aug. 31, 2020
  • Laurairsone

    Jul. 29, 2020
  • MuhammedGalibUluda

    Jul. 23, 2020
  • ThomasSchulz41

    Jul. 3, 2020
  • RobinTheriault1

    Jun. 29, 2020
  • FabioAgostinhoBoris

    Jun. 19, 2020
  • PabloBrianese

    Jun. 17, 2020
  • SatyaPudi

    May. 19, 2020
  • larsthorup

    May. 17, 2020
  • ashok7979

    Apr. 11, 2020

Programming is hard. Programming correct C and C++ is particularly hard. Indeed, both in C and certainly in C++, it is uncommon to see a screenful containing only well defined and conforming code.Why do professional programmers write code like this? Because most programmers do not have a deep understanding of the language they are using.While they sometimes know that certain things are undefined or unspecified, they often do not know why it is so. In these slides we will study small code snippets in C and C++, and use them to discuss the fundamental building blocks, limitations and underlying design philosophies of these wonderful but dangerous programming languages. This content has a CC license. Feel free to use it for whatever you want. You may download the original PDF file from: http://www.pvv.org/~oma/DeepC_slides_oct2012.pdf

Views

Total views

1,221,816

On Slideshare

0

From embeds

0

Number of embeds

38,470

Actions

Downloads

21,386

Shares

0

Comments

0

Likes

1,521

×