meghshah09 Goto Github PK

campustour-scheduling-using-builder-pattern

computer-architecture-5-stage-pipeline-simulator-version-1

computer-architecture-5-stage-pipeline-simulator-version-2

computer-architecture-5-stage-pipeline-simulator-version-3

The processor to be simulated has the following features:  It has the same instructions as the processor you simulated for Project 2. The function units are also the same as in Project 2.  It uses register renaming with an IQ, ROB and LSQ. A physical register file is used, along with an architectural register file. The issue queue entry holds literal operands and all register operand values.  LOADs can bypass earlier STOREs in the LSQ when the bypassing conditions hold. A LOAD can also pick up the queued value to be stored from the LSQ entry of the nearest preceding STORE if they both target the same memory location.  Memory addresses are calculated on the IntFU and written to the LSQ entry for LOADs and STOREs. Memory accesses take place from the head of the LSQ using the stage MEM, which is not pipelined and has a 3-cycle delay. Each memory access thus takes 3 cycles. Fetch D/RF MUL1 MUL2 Int. FU DU2 DU1 DU3 DU4 IQ LSQ ROB MEM ARF PRF and connections to PRF are not shown  Four forwarding/broadcast buses exist to the IQ for simultaneous use by the IntFU, DIV FU, MUL FU and MEM in a single cycle if needed. The physical register file, IQ, LSQ and ROB each have enough ports to support as many concurrent reads and writes that are needed in a single cycle.  All decoding, renaming and dispatch steps are performed in a single D/RF stage.  The processor supports back-to-back execution, with the tag (which is a physical register address) broadcasted one cycle before the result is available.  As in Project 2, the target address of the branches, JUMP and JAL are computed in the IntFU.  A field is added to every physical register to hold the flag value produced along with the result held in the physical register. For project 2, the ONLY flag that you have to deal with is the Z flag, so you will need an 1-bit extension for each physical register. As an example, when you have a SUB instruction that uses physical register P5 as an destination, store the result of the SUB in P5 and hold the Z flag produced by the SUB was a zero or not in the 1-bit extension of P5. The rename table will need an entry for the Z flag. The configuration details on the number/capacities of the key datapath components are as: Architectural registers: 16 (Numbered 0 to 15), Physical registers: 32 (Numbered 0 to 31) IQ capacity : 16 entries, ROB capacity: 32 entries, LSQ capacity: 32 entries All other functional requirements for the simulator are as in Project 2. The "display" command needs to print the contents of all major components that are simulated (rename table, LSQ, IQ, ROB, PRF, Fetch PC, elapsed cycles, CPI up to the last simulated cycle etc.

cs550-18s-proj0-mshah31

cs575--project-3_knapsack_huffman

Knapsack Using Backtracking, Bruteforce and Dynamic Programing

cs575-assignment2

Floyd, OBST, Tromino Tiling

expense_tracker

hackerrank

heart-disease-prediction-using-data-mining-techniques_v1.0

inayo_web_front

machine_learning_python

Small Machine Learning Projects Using Python Libraries

mlfq_scheduling_in_xv6

mongodbstitchapplicationtutorial

Last five Login Activities

oacomps

A Component Framework based on React.js and Bulma

phone-directory-cs575-assignment1

railway-reservation-ticketing-system

react-forms

react-grid

reactstarter

sayaniacatering

Sayania Catering Android Application

search-engine

project 1 consists of basic command line to project 5 which is based on SPA using React.js

serialization-and-deserialization-of-objects-using-reflection

sniffer

sp-500-stock-price-forecasting

student-course-planner-using-state-pattern

student-courses-backup-system

CS542 : Design Pattern. Implemented Student Courses Backup System using BST and Observer Pattern

tourist-guide

Tourist Guide Android Application with three Different Paradigms Used.

trouble-shootsearch-using-visitor-pattern

tts_project