Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

+ - Ask Slashdot: How Many (Electronics) Gates Is That Software Algorithm?

Submitted by dryriver
dryriver (1010635) writes "Dear Slashdotters: We have developed a graphics algorithm that got an electronics manufacturer interested in turning it into hardware. Here comes the problematic bit... The electronics manufacturer asked us to describe how complex the algorithm is. More specifically, we were asked "How many (logic) gates would be needed to turn your software algorithm into hardware?" This threw us a bit, since none of us have done electronics design before. So here is the question: Is there are a software or other tool that can analyze an algorithm written in C/C++ and estimate how many gates would be needed to turn it into hardware? Or, perhaps, there is a more manual method of converting code lines to gates? Maybe an operation like "Add" would require 3 gates while an operation like "Divide" would need 6 gates? Something like this anyway... To state the question one more time: How do we get from a software algorithm that is N lines long and executes X number of total operations overall, to a rough estimate of how many gates this algorithm would use when translated into electronic hardware?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Ask Slashdot: How Many (Electronics) Gates Is That Software Algorithm?

Comments Filter:

A formal parsing algorithm should not always be used. -- D. Gries

Working...