Corning Community College
CSCS2650 Computer Organization
PROJECT: Prime Number Computation (PNC1)
OBJECTIVE
Continue exploring algorithm/implementation comparison and optimization with respect to various approaches of computing prime numbers.
TASK
Add to your two separate, independent programs, one in Vircon32 C, and other in Vircon32 assembly, functionality that:
implements individual and combined functionality for the following optimizations (both in C and assembly):
odds: above 2, does odds-only processing (both number and factor check)
break: breaks from trial division/brute force when a viable factor is found (break on composite)
sqrt: only processes up through the square root point of the number being evaluated
possibilities here include the 3 identified variants (odds, break, sqrt) along with their combinations (odds+break, odds+sqrt, break+sqrt, odds+break+sqrt)
collects the same timing data with common workloads to the brute force variants from pnc0
new variants added to the runtime graph you made in pnc0, adjusting and re-running pnc0 variants to allow for a consistent presentation of information
you may consider a lower upper-bound runtime threshold for the pnc1 variants (perhaps somewhere between 2 and 8 seconds, compared to the 16 seconds for pnc0).
REFERENCE
The following are reference screenshots of what your implementations should approximate.
PNC1
C implementation
EDIT
You will want to go here to edit and fill in the various sections of the document:
SUBMISSION
To be successful in this project, the following criteria (or their equivalent) must be met:
Project must be submit on time, by the deadline.
Executed programs must display in a manner similar to provided output
Processing must be correct based on input given and output requested
Output, if applicable, must be correct based on values input
Code must be nicely and consistently indented
Code must be consistently written, to strive for readability from having a consistent style throughout
Code must be commented
No global variables (without instructor approval), no goto statements, no calling of main()!
Track/version the source code in your lab46 semester repository
Submit a copy of your source code to me using the submit tool by the deadline.
Let's say you have completed work on the project, and are ready to
submit, you would do the following:
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
You should get some sort of confirmation indicating successful submission
if all went according to plan. If not, check for typos and or locational
mismatches.
RUBRIC
I'll be evaluating the project based on the following criteria:
286:pnc1:final tally of results (286/286)
*:pnc1:submitted C and assembly implementations [26/26]
*:pnc1:each implementation builds cleanly [26/26]
*:pnc1:output conforms to specifications [26/26]
*:pnc1:processing is correct, and to specifications [26/26]
*:pnc1:working break on composite optimization [26/26]
*:pnc1:working odds only processing optimization [26/26]
*:pnc1:working sqrt factor cap optimization [26/26]
*:pnc1:all variants and combinations thereof operational [26/26]
*:pnc1:graph produced from timing data produced [26/26]
*:pnc1:graph posted to discord and documentation page [26/26]
*:pnc1:timing data is taken out to 3 decimal places [26/26]
Pertaining to the collaborative authoring of project documentation
Additionally
Solutions not abiding by spirit of project will be subject to a 50% overall deduction
Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction