Great Deal! Get Instant $10 FREE in Account on First Order + 10% Cashback on Every Order Order Now

datalab-handout/bits.h /* Copyright (C XXXXXXXXXXFree 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...

1 answer below »
datalab-handout
its.h
* Copyright (C XXXXXXXXXXFree Software Foundation, Inc.
This file is part of the GNU C Li
ary.
The GNU C Li
ary is free software; you can redistribute it and/o
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; eithe
version 2.1 of the License, or (at your option) any later version.
The GNU C Li
ary is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied wa
anty 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 Li
ary; if not, see
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 or any other header that includes
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 Unicode XXXXXXXXXXVersion 10.0 of the Unicode Standard is
synchronized with ISO/IEC 10646:2017, fifth edition, plus
the following additions from Amendment 1 to the fifth edition:
XXXXXXXXXXemoji characters
XXXXXXXXXXhentaigana
- 3 additional Zanabazar Square characters *
* We do not support C11 . *
***************************************************
* BOOLEAN operations (8 puzzles, 18 points total) *
***************************************************
int bitOr(int, int);
int test_bitOr(int, int);
int bitAnd(int, int);
int test_bitAnd(int, int);
int bitXor(int, int);
int test_bitXor(int, int);
int isNotEqual(int, int);
int test_isNotEqual(int, int);
int copyLSB(int);
int test_copyLSB(int);
int specialBits();
int test_specialBits();
int conditional(int, int, int);
int test_conditional(int, int, int);
int bitParity(int);
int test_bitParity(int);
*******************************************
* INTEGERS (8 puzzles, 22 points total) *
*******************************************
int minusOne();
int test_minusOne();
int tmax();
int test_tmax();
int negate(int);
int test_negate(int);
int isNegative(int);
int test_isNegative(int);
int isPositive(int);
int test_isPositive(int);
int bang(int);
int test_bang(int);
int addOK(int, int);
int test_addOK(int, int);
int absVal(int);
int test_absVal(int);
*************************************************************
* BONUS puzzles BELOW! be advised, some are quite difficult *
************************************************************
***************************************************
INTEGERS and BOOLEAN (3 puzzles, up to 10 points) *
***************************************************
int byteSwap(int, int, int);
int test_byteSwap(int, int, int);
int bitCount(int);
int test_bitCount(int);
int logicalShift(int, int);
int test_logicalShift(int, int);
datalab-handout/Driverhdrs.pm
#
# This file contains configuration variables for drivers.
# It was generated by genhdrs.pl. Do not modify it.
#
package Driverhdrs;
$LAB = "datalab";
$SERVER_NAME = "2467.cs.uno.edu";
$SERVER_PORT = 8081;
$COURSE_NAME = "csapp";
$AUTOGRADE_TIMEOUT = 0;
1;
datalab-handout/README
***********************
The CS:APP Data La
Directions to Students
***********************
Your goal is to modify your copy of bits.c so that it passes all the
tests in btest without violating any of the coding guidelines.
*********
0. Files:
*********
Makefile    - Makes btest, fshow, and ishow
README        - This file
its.c        - The file you will be modifying and handing in
its.h        - Header file
test.c        - The main btest program
btest.h    - Used to build btest
decl.c    - Used to build btest
tests.c XXXXXXXXXXUsed to build btest
tests-header.c- Used to build btest
dlc*        - Rule checking compiler binary (data lab compiler)    
driver.pl*    - Driver program that uses btest and dlc to autograde bits.c
Driverhdrs.pm - Header file for optional "Beat the Prof" contest
fshow.c        - Utility for examining floating-point representations
ishow.c        - Utility for examining integer representations
***********************************************************
1. Modifying bits.c and checking it for compliance with dlc
***********************************************************
IMPORTANT: Carefully read the instructions in the bits.c file before
you start. These give the coding rules that you will need to follow if
you want credit for your work.
Use the dlc compiler (./dlc) to automatically check your version of
its.c for compliance with the coding guidelines:
unix> ./dlc bits.c
dlc returns silently if there are no problems with your code.
Otherwise it prints messages that flag any problems. Running dlc with
the -e switch:
    unix> ./dlc -e bits.c
causes dlc to print counts of the number of operators used by each function.
Once you have a legal solution, you can test it for co
ectness using
the .
test program.
*********************
2. Testing with btest
*********************
The Makefile in this directory compiles your version of bits.c with
additional code to create a program (or test harness) named btest.
To compile and run the btest program, type:
unix> make btest
unix> .
test [optional cmd line args]
You will need to recompile btest each time you change your bits.c
program. When moving from one platform to another, you will want to
get rid of the old version of btest and generate a new one. Use the
commands:
unix> make clean
unix> make btest
Btest tests your code for co
ectness by running millions of test
cases on each function. It tests wide swaths around well known corne
cases such as Tmin and zero for integer puzzles, and zero, inf, and
the boundary between denormalized and normalized numbers for floating
point puzzles. When btest detects an e
or in one of your functions,
it prints out the test that failed, the inco
ect result, and the
expected result, and then terminates the testing for that function.
Here are the command line options for btest:
unix> .
test -h
Usage: .
test [-hg] [-r ] [-f [-1|-2|-3 ]*] [-T
Answered 4 days After Sep 22, 2021

Solution

Karthi answered on Sep 26 2021
143 Votes
71_cpp_91794/Driverhdrs.pm
#
# This file contains configuration variables for drivers.
# It was generated by genhdrs.pl. Do not modify it.
#
package Driverhdrs;
$LAB = "datalab";
$SERVER_NAME = "2467.cs.uno.edu";
$SERVER_PORT = 8081;
$COURSE_NAME = "csapp";
$AUTOGRADE_TIMEOUT = 0;
1;
71_cpp_91794/Driverlib.pm
###############################################################
# Driverlib.pm - A package of helper functions for Perl drivers
#
# Copyright (c) 2005 David R. O'Hallaron, All rights reserved.
###############################################################
package Driverlib;
use Socket;
# Autogenerated header file with lab-specific constants
use lib ".";
use Driverhdrs;
equire Exporter;
@ISA = qw(Exporter);
@EXPORT = qw(
     driver_post
     );
use strict;
#####
# Public functions
#
#
# driver_post - This is the routine that a driver calls when
# it needs to transmit an autoresult string to the result server.
#
sub driver_post ($$) {
my $userid = shift; # User id for this submission
my $result = shift; # Autoresult string
my $autograded = shift; # Set if called by an autograde
# Echo the autoresult string to stdout if the driver was called
# by an autograde
if ($autograded) {
print "\n";
print "AUTORESULT_STRING=$result\n";
return;
}    
# If the driver was called with a specific userid, then submit
# the autoresult string to the result server over the Internet.
if ($userid) {
my $status = submitr($Driverhdrs::SERVER_NAME,
$Driverhdrs::SERVER_PORT,
$Driverhdrs::COURSE_NAME,
$userid,
$Driverhdrs::LAB,
$result);

# Print the status of the transfe
if (!($status =~ /OK/)) {
print "$status\n";
print "Did not send autoresult string to the result server.\n";
exit(1);
}
print "Success: Sent autoresult string for $userid to the result server.\n";
}    
}
#####
# Private functions
#
#
# submitr - Sends an autoresult string to the result serve
#
sub submitr ($$$$$$) {
my $hostname = shift;
my $port = shift;
my $course = shift;
my $userid = shift;
my $lab = shift;
my $result = shift;
my $internet_addr;
my $enc_result;
my $paddr;
my $line;
my $http_version;
my $e
code;
my $e
msg;
# Establish the connection to the serve
socket(SERVER, PF_INET, SOCK_STREAM, getprotobyname('tcp'));
$internet_addr = inet_aton($hostname)
or die "Could not convert $hostname to an internet address: $!\n";
$paddr = sockaddr_in($port, $internet_addr);
connect(SERVER, $paddr)
or die "Could not connect to $hostname:$port:$!\n";
select((select(SERVER), $| = 1)[0]); # enable command buffering
# Send HTTP request to serve
$enc_result = url_encode($result);
print SERVER "GET /$course/submitr.pl/?userid=$userid&lab=$lab&result=$enc_result&submit=submit HTTP/1.0\r\n\r\n";
# Get first HTTP response line
$line = ;
chomp($line);
($http_version, $e
code, $e
msg) = split(/\s+/, $line);
if ($e
code != 200) {
return "E
or: HTTP request failed with e
or $e
code: $e
msg";
}
# Read the remaining HTTP response header lines
while ($line = ) {
if ($line =~ /^\r\n/) {
last;
}
}
# Read and return the response from the result serve
$line = ;
chomp($line);
close SERVER;
return $line;

}
#
# url_encode - Encode text string so it can be included in URI of GET request
#
sub url_encode ($) {
my $value = shift;
$value =~s/([^a-zA-Z0-9_\-.])/uc sprintf("%%%02x",ord($1))/eg;
return $value;
}
# Always end a module with a 1 so that it returns TRUE
1;
71_cpp_91794/Makefile
#
# Makefile that builds btest and other helper programs for the CS:APP data la
#
CC = gcc
CFLAGS = -O -g -Wall -m32 -Wno-bool-operation
LIBS = -lm
all: btest fshow ishow
test: btest.c bits.c decl.c tests.c btest.h bits.h
    $(CC) $(CFLAGS) $(LIBS) -o btest bits.c btest.c decl.c tests.c
fshow: fshow.c
    $(CC) $(CFLAGS) -o fshow fshow.c
ishow: ishow.c
    $(CC) $(CFLAGS) -o ishow ishow.c
# Forces a recompile. Used by the driver program.
testexplicit:
    $(CC) $(CFLAGS) $(LIBS) -o btest bits.c btest.c decl.c tests.c
clean:
    rm -f *.o btest fshow ishow *~
71_cpp_91794/README
***********************
The CS:APP Data La
Directions to Students
***********************
Your goal is to modify your copy of bits.c so that it passes all the
tests in btest without violating any of the coding guidelines.
*********
0. Files:
*********
Makefile    - Makes btest, fshow, and ishow
README        - This file
its.c        - The file you will be modifying and handing in
its.h        - Header file
test.c        - The main btest program
btest.h    - Used to build btest
decl.c    - Used to build btest
tests.c - Used to build btest
tests-header.c- Used to build btest
dlc*        - Rule checking compiler binary (data lab compiler)    
driver.pl*    - Driver program that uses btest and dlc to autograde bits.c
Driverhdrs.pm - Header file for optional "Beat the Prof" contest
fshow.c        - Utility for examining floating-point representations
ishow.c        - Utility for examining integer representations
***********************************************************
1. Modifying bits.c and checking it for compliance with dlc
***********************************************************
IMPORTANT: Carefully read the instructions in the bits.c file before
you start. These give the coding rules that you will need to follow if
you want credit for your work.
Use the dlc compiler (./dlc) to automatically check your version of
its.c for compliance with the coding guidelines:
unix> ./dlc bits.c
dlc returns silently if there are no problems with your code.
Otherwise it prints messages that flag any problems. Running dlc with
the -e switch:
    unix> ./dlc -e bits.c
causes dlc to print counts of the number of operators used by each function.
Once you have a legal solution, you can test it for co
ectness using
the .
test program.
*********************
2. Testing with btest
*********************
The Makefile in this directory compiles your version of bits.c with
additional code to create a program (or test harness) named btest.
To compile and run the btest program, type:
unix> make btest
unix> .
test [optional cmd line args]
You will need to recompile btest each time you change your bits.c
program. When moving from one platform to another, you will want to
get rid of the old version of btest and generate a new one. Use the
commands:
unix> make clean
unix> make btest
Btest tests your code for co
ectness by running millions of test
cases on each function. It tests wide swaths around well known corne
cases such as Tmin and zero for integer puzzles, and zero, inf, and
the boundary between denormalized and normalized numbers for floating
point puzzles. When btest detects an e
or in one of your functions,
it prints out the test that failed, the inco
ect result, and the
expected result, and then terminates the testing for that function.
Here are the command line options for btest:
unix> .
test -h
Usage: .
test [-hg] [-r ] [-f [-1|-2|-3 ]*] [-T
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here