본문으로 바로가기

[Datalab-handout] bits.c

category C&C++ 2017. 10. 6. 19:49

/* 

 * CS:APP Data Lab 

 * 

 * 

 * 

 * bits.c - Source file with your solutions to the Lab.

 *          This is the file you will hand in to your instructor.

 *

 * WARNING: Do not include the <stdio.h> header; it confuses the dlc

 * compiler. You can still use printf for debugging without including

 * <stdio.h>, although you might get a compiler warning. In general,

 * it's not good practice to ignore compiler warnings, but in this

 * case it's OK.  

 */


#if 0

/*

 * Instructions to Students:

 *

 * STEP 1: Read the following instructions carefully.

 */


You will provide your solution to the Data Lab by

editing the collection of functions in this source file.


INTEGER CODING RULES:

 

  Replace the "return" statement in each function with one

  or more lines of C code that implements the function. Your code 

  must conform to the following style:

 

  int Funct(arg1, arg2, ...) {

      /* brief description of how your implementation works */

      int var1 = Expr1;

      ...

      int varM = ExprM;


      varJ = ExprJ;

      ...

      varN = ExprN;

      return ExprR;

  }


  Each "Expr" is an expression using ONLY the following:

  1. Integer constants 0 through 255 (0xFF), inclusive. You are

      not allowed to use big constants such as 0xffffffff.

  2. Function arguments and local variables (no global variables).

  3. Unary integer operations ! ~

  4. Binary integer operations & ^ | + << >>

    

  Some of the problems restrict the set of allowed operators even further.

  Each "Expr" may consist of multiple operators. You are not restricted to

  one operator per line.


  You are expressly forbidden to:

  1. Use any control constructs such as if, do, while, for, switch, etc.

  2. Define or use any macros.

  3. Define any additional functions in this file.

  4. Call any functions.

  5. Use any other operations, such as &&, ||, -, or ?:

  6. Use any form of casting.

  7. Use any data type other than int.  This implies that you

     cannot use arrays, structs, or unions.


 

  You may assume that your machine:

  1. Uses 2s complement, 32-bit representations of integers.

  2. Performs right shifts arithmetically.

  3. Has unpredictable behavior when shifting an integer by more

     than the word size.


EXAMPLES OF ACCEPTABLE CODING STYLE:

  /*

   * pow2plus1 - returns 2^x + 1, where 0 <= x <= 31

   */

  int pow2plus1(int x) {

     /* exploit ability of shifts to compute powers of 2 */

     return (1 << x) + 1;

  }


  /*

   * pow2plus4 - returns 2^x + 4, where 0 <= x <= 31

   */

  int pow2plus4(int x) {

     /* exploit ability of shifts to compute powers of 2 */

     int result = (1 << x);

     result += 4;

     return result;

  }


FLOATING POINT CODING RULES


For the problems that require you to implent floating-point operations,

the coding rules are less strict.  You are allowed to use looping and

conditional control.  You are allowed to use both ints and unsigneds.

You can use arbitrary integer and unsigned constants.


You are expressly forbidden to:

  1. Define or use any macros.

  2. Define any additional functions in this file.

  3. Call any functions.

  4. Use any form of casting.

  5. Use any data type other than int or unsigned.  This means that you

     cannot use arrays, structs, or unions.

  6. Use any floating point data types, operations, or constants.



NOTES:

  1. Use the dlc (data lab checker) compiler (described in the handout) to 

     check the legality of your solutions.

  2. Each function has a maximum number of operators (! ~ & ^ | + << >>)

     that you are allowed to use for your implementation of the function. 

     The max operator count is checked by dlc. Note that '=' is not 

     counted; you may use as many of these as you want without penalty.

  3. Use the btest test harness to check your functions for correctness.

  4. Use the BDD checker to formally verify your functions

  5. The maximum number of ops for each function is given in the

     header comment for each function. If there are any inconsistencies 

     between the maximum ops in the writeup and in this file, consider

     this file the authoritative source.


/*

 * STEP 2: Modify the following functions according the coding rules.

 * 

 *   IMPORTANT. TO AVOID GRADING SURPRISES:

 *   1. Use the dlc compiler to check that your solutions conform

 *      to the coding rules.

 *   2. Use the BDD checker to formally verify that your solutions produce 

 *      the correct answers.

 */



#endif

/* Copyright (C) 1991-2014 Free Software Foundation, Inc.

   This file is part of the GNU C Library.


   The GNU C Library is free software; you can redistribute it and/or

   modify it under the terms of the GNU Lesser General Public

   License as published by the Free Software Foundation; either

   version 2.1 of the License, or (at your option) any later version.


   The GNU C Library is distributed in the hope that it will be useful,

   but WITHOUT ANY WARRANTY; without even the implied warranty of

   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU

   Lesser General Public License for more details.


   You should have received a copy of the GNU Lesser General Public

   License along with the GNU C Library; if not, see

   <http://www.gnu.org/licenses/>.  */

/* This header is separate from features.h so that the compiler can

   include it implicitly at the start of every compilation.  It must

   not itself include <features.h> or any other header that includes

   <features.h> because the implicit include comes before any feature

   test macros that may be defined in a source file before it first

   explicitly includes a system header.  GCC knows the name of this

   header in order to preinclude it.  */

/* glibc's intent is to support the IEC 559 math functionality, real

   and complex.  If the GCC (4.9 and later) predefined macros

   specifying compiler intent are available, use them to determine

   whether the overall intent is to support these features; otherwise,

   presume an older compiler has intent to support these features and

   define these macros by default.  */

/* wchar_t uses ISO/IEC 10646 (2nd ed., published 2011-03-15) /

   Unicode 6.0.  */

/* We do not support C11 <threads.h>.  */

/* 

 * bitAnd - x&y using only ~ and | 

 *   Example: bitAnd(6, 5) = 4

 *   Legal ops: ~ |

 *   Max ops: 8

 *   Rating: 1

 */

int bitAnd(int x, int y) {

int result = ~x|~y;


  return ~result;

}

/* 

 * getByte - Extract byte n from word x

 *   Bytes numbered from 0 (LSB) to 3 (MSB)

 *   Examples: getByte(0x12345678,1) = 0x56

 *   Legal ops: ! ~ & ^ | + << >>

 *   Max ops: 6

 *   Rating: 2

 */

int getByte(int x, int n) {

int a = n << 3;

int shift_x = x >> a;

  return shift_x&0xff;

}

/* 

 * logicalShift - shift x to the right by n, using a logical shift

 *   Can assume that 0 <= n <= 31

 *   Examples: logicalShift(0x87654321,4) = 0x08765432

 *   Legal ops: ! ~ & ^ | + << >>

 *   Max ops: 20

 *   Rating: 3 

 */

int logicalShift(int x, int n) {


int shift_x = x>>n;

int a = 1<<31;

a = (a>>n) << 1;


return shift_x & (~a);

}

/*

 * bitCount - returns count of number of 1's in word

 *   Examples: bitCount(5) = 2, bitCount(7) = 3

 *   Legal ops: ! ~ & ^ | + << >>

 *   Max ops: 40

 *   Rating: 4

 */

int bitCount(int x) {

int a = 0x11;

int b;

int result;

a = (a << 8) + a;

a = (a << 16) + a;


b = x & a;

b += (x >> 1)&a;

b += (x >> 2)&a;

b += (x >> 3)&a;

b += (b >> 16);


result = b&0x0f;

result += (b>>4)&0x0f;

result += (b>>8)&0x0f;

result += (b>>12)&0x0f;


  return result;

}

/*

 * isZero - returns 1 if x == 0, and 0 otherwise 

 *   Examples: isZero(5) = 0, isZero(0) = 1

 *   Legal ops: ! ~ & ^ | + << >>

 *   Max ops: 2

 *   Rating: 1

 */

int isZero(int x) {

return !x;

}

/* 

 * isEqual - return 1 if x == y, and 0 otherwise 

 *   Examples: isEqual(5,5) = 1, isEqual(4,5) = 0

 *   Legal ops: ! ~ & ^ | + << >>

 *   Max ops: 5

 *   Rating: 2

 */

int isEqual(int x, int y) {

int result = x^y;


return !result;

}

/* 

 * fitsBits - return 1 if x can be represented as an 

 *  n-bit, two's complement integer.

 *   1 <= n <= 32

 *   Examples: fitsBits(5,3) = 0, fitsBits(-4,3) = 1

 *   Legal ops: ! ~ & ^ | + << >>

 *   Max ops: 15

 *   Rating: 2

 */

int fitsBits(int x, int n) {

int result = (x<<(33+~n)) >> (33+~n);


  return !(result^x);

}

/* 

 * isLessOrEqual - if x <= y  then return 1, else return 0 

 *   Example: isLessOrEqual(4,5) = 1.

 *   Legal ops: ! ~ & ^ | + << >>

 *   Max ops: 24

 *   Rating: 3

 */

int isLessOrEqual(int x, int y) {

int sx =(x >> 31)&1;

int sy =(y >> 31)&1;


int a = (sx^sy) & sx;


int b = !(sx^sy) & (((x + ~y) >> 31)&1);

  return (a|b);

}

/* 

 * rotateLeft - Rotate x to the left by n

 *   Can assume that 0 <= n <= 31

 *   Examples: rotateLeft(0x87654321,4) = 0x76543218

 *   Legal ops: ~ & ^ | + << >> !

 *   Max ops: 25

 *   Rating: 3 

 */

int rotateLeft(int x, int n) {

int a = ~(~0 << n);

int b = 33+~n;


b = (x >> b);

b = a&b;



  return b+(x<<n);

}

'C&C++' 카테고리의 다른 글

Simple BlackJack  (0) 2017.11.12