C job interview - casting and comparing

后端 未结 10 713
没有蜡笔的小新
没有蜡笔的小新 2021-02-01 12:29

I was confronted with a tricky (IMO) question. I needed to compare two MAC addresses, in the most efficient manner.

The only thought that crossed my mind in that moment

相关标签:
10条回答
  • 2021-02-01 12:42

    To do type punning correctly you have to use an union. Otherwise you will break the rules strict aliasing which certain compilers follow, and the result will be undefined.

    int EqualMac( MAC* a , MAC* b )
    {
        union
        {
            MAC m ;
            uint16_t w[3] ;
    
        } ua , ub ;
    
        ua.m = *a ;
        ub.m = *b ;
    
        if( ua.w[0] != ub.w[0] )  
            return 0 ;
    
        if( ua.w[1] != ub.w[1] )
            return 0 ;
    
        if( ua.w[2] != ub.w[2] )
            return 0 ;
    
    return 1 ;
    }
    

    According to C99 it is safe to read from an union member that is not the last used to store a value in it.

    If the member used to read the contents of a union object is not the same as the member last used to store a value in the object, the appropriate part of the object representation of the value is reinterpreted as an object representation in the new type as described in 6.2.6 (a process sometimes called "type punning"). This might be a trap representation.

    0 讨论(0)
  • 2021-02-01 12:43

    Function memcmp will eventually do the loop itself. So by using it, you would basically just make things less efficient (due to the additional function-call).

    Here is an optional solution:

    typedef struct
    {
        int x;
        short y;
    }
    MacAddr;
    
    int isEqual(MAC* addr1, MAC* addr2)
    {
        return *(MacAddr*)addr1 == *(MacAddr*)addr2;
    }
    

    The compiler will most likely convert this code into two comparisons, since the MacAddr structure contains two fields.

    Cavity: unless your CPU supports unaligned load/store operations, addr1 and addr2 must be aligned to 4 bytes (i.e., they must be located in addresses that are divisible by 4). Otherwise, a memory access violation will most likely occur when the function is executed.

    You may divide the structure into 3 fields of 2 bytes each, or 6 fields of 1 byte each (reducing the alignment restriction to 2 or 1 respectively). But bare in mind that a single comparison in your source code is not necessarily a single comparison in the executable image (i.e., during runtime).

    BTW, unaligned load/store operations by themselves may add runtime latency, if they require more "nops" in the CPU pipeline. This is really a matter of CPU architecture, which I doubt they meant to "dig into" that far in your job interview. However, in order to assert that the compiled code does not contain such operations (if indeed they are "expensive"), you could ensure that the variables are always aligned to 8 bytes AND add a #pragma (compiler directive) telling the compiler "not to worry about this".

    0 讨论(0)
  • 2021-02-01 12:48

    If your interviewer demands that you produce undefined behavior, I would probably look for a job elsewhere.

    The correct initial approach would be to store the MAC address in something like a uint64_t, at least in-memory. Then comparisons would be trivial, and implementable efficiently.

    0 讨论(0)
  • 2021-02-01 12:51

    May be he had in mind a definition of MAC that used unsigned char and was thinking to:

    int isEqual(MAC* addr1, MAC* addr2) { return strncmp((*addr1).data,(*addr2).data,6)==0; }

    which implies a cast from (unsigned char *) to (char *). Anyway bad question.

    0 讨论(0)
  • 2021-02-01 12:53

    Non-portable casting solution.

    In a platform I use (PIC24 based), there is a type int48, so making a safe assumption char is 8 bits and the usual alignment requirements:

    int isEqual(MAC* addr1, MAC* addr2) {
      return *((int48_t*) &addr1->data) == *((int48_t*) &addr2->data);
    }
    

    Of course, this is not usable on many platforms, but then so are a number of solutions that are not portable either, depending on assumed int size, no padding, etc.

    The highest portable solution (and reasonably fast given a good compiler) is the memcmp() offered by @H2CO3.

    Going to a higher design level and using a wide enough integer type like uint64_t instead of struct macA, as suggested by Kerrek SB, is very appealing.

    0 讨论(0)
  • 2021-02-01 12:55

    Cowboy time:

    typedef struct macA {
       char data[6];
    } MAC;
    
    typedef struct sometimes_works {
       long some;
       short more;
    } cast_it
    
    typedef union cowboy
    {
        MAC real;
        cast_it hack;
    } cowboy_cast;
    
    int isEqual(MAC* addr1, MAC* addr2)
    {
         assert(sizeof(MAC) == sizeof(cowboy_cast));  // Can't be bigger
         assert(sizeof(MAC) == sizeof(cast_it));      // Can't be smaller
    
         if ( ( ((cowboy_cast *)addr1)->hack.some == ((cowboy_cast *)addr2)->hack.some )
           && ( ((cowboy_cast *)addr1)->hack.more == ((cowboy_cast *)addr2)->hack.more ) )
                 return (0 == 0);
    
         return (0 == 42);
    }
    
    0 讨论(0)
提交回复
热议问题