Quartus complaint: My LOOP is too big? But the code is from the book, what's wrong?

You realise there is a big difference between HDL and procedural languages right?

Loops make little sense in hardware - it doesn't run as a loop, the synthesizer breaks it all up into hardware - so if you did a loop that added 1 four times, it would probably make a chain of four adders each adding 1.

In your case, how does the synthesizer know when to stop? If ctrl_align was say 10, it would require 10 copies of the hardware. If it was 20, it would require 20 copies of the hardware. So how does it know how many to put?

--- Quote Start ---

You realise there is a big difference between HDL and procedural languages right?

Loops make little sense in hardware - it doesn't run as a loop, the synthesizer breaks it all up into hardware - so if you did a loop that added 1 four times, it would probably make a chain of four adders each adding 1.

In your case, how does the synthesizer know when to stop? If ctrl_align was say 10, it would require 10 copies of the hardware. If it was 20, it would require 20 copies of the hardware. So how does it know how many to put?

--- Quote End ---

Yes sir, I have been reading more information and I understand what you say. Although, I'd like to point that this code is from book itself. I'm learning Verilog just recently, and Bibliography is very confusing and contradictory for a beginner. I was trying to make Floating Point operation, and Cavanagh book take this behavioral path. So I wonder, if is senseless to make such of operations by this way, why to write a whole book under this concept, while it should really be implemented differently? This is not a general book, it is about arithmetic in verilog. My first impression was that, it would be ok to use this model, and there is not a better way.

What way do you personally would suggest, considering this is a hypothetical real life implementation?

One more thing, it seems that is possible to Set .qsf files to a different number, Quartus complaint that 250 is the highest set, and my ctrl_aligh is 8 bits, that would be 255, so I just need to change that setting in the files?

The code from the book looks like it was written for use in a simulator. This code clearly cannot be synthesized.

Are you are studying how to develop hardware for doing floating point? Unless that is the case, using floating point in an FPGA is not the best solution. If your goal is to do a parallel calculation, you should convert your problem domain to integer or fixed point. Nearly every computation using physical world data can be done with integers or fixed point. Study numerical methods to see how this is done. Once you've converted your problem space then you can start your FPGA work.

--- Quote Start ---

The code from the book looks like it was written for use in a simulator. This code clearly cannot be synthesized.

Are you are studying how to develop hardware for doing floating point? Unless that is the case, using floating point in an FPGA is not the best solution. If your goal is to do a parallel calculation, you should convert your problem domain to integer or fixed point. Nearly every computation using physical world data can be done with integers or fixed point. Study numerical methods to see how this is done. Once you've converted your problem space then you can start your FPGA work.

--- Quote End ---

I'm not sure what parallel calculation means, but isn't exactly what the above code is trying to do? It is, to separate exponents and fractions and consider them Integers, doing subsequent separated evaluations. Yet, it needs of this awkward loops. If is not, what is this numerical method which I should search for?

Now, I understand if I follow the book's method, Quartus will end generating at least 255 (If I manage to set configuration files) hardware units, which may or may not be used depending of the value reached by "ctrl_align", I wonder, is this completly wrong to do if my goal is not only to simulate but to actually fabricate a chip?

I will briefly explain what I'm trying to do, you may remember something of my previous posts.

I want to design a chip, this chip performs the calculation of an equation known as "FCM" (Fuzzy C means). Equation itself includes iterative additions, subtraction, multiplication and division. Because it performs iterative divisions, fractional numbers are necessary, otherwise It will end giving me a wrong results. From my point of view, I should create a logic in Verilog able to do this, using Quartus and Synthesis simulation of what should become in a chip later. So, is this the way to do it, or am I wrong?

I've searched in internet, there is a lot of material regarding Floating Point operations in verilog, they say efficient, but efficient enough for a real chip? Idk

--- Quote Start ---

Just because you can write HDL doesnt mean it makes sense in hardware. HDL is also meant to produce behavioral code to aid simulation that is not for use in a real design.

--- Quote End ---

I was under the conception that HDL is for designing chips or hardware itself, so what's the point to make a book with no synthesizable coding in HDL in the first instance. I can understand it for Test Benchs because they won't become a chip ever.

Updating:

If direct verilog isn't correct for doing this kind of operation, would it be a better way to design a kind of processor, with registers, stacks, simple add and subs? I know I could easily do this equation in Assembly.

--- Quote Start ---

I was under the conception that HDL is for designing chips or hardware itself, so what's the point to make a book with no synthesizable coding in HDL in the first instance. I can understand it for Test Benchs because they won't become a chip ever.

Updating:

If direct verilog isn't correct for doing this kind of operation, would it be a better way to design a kind of processor, with registers, stacks, simple add and subs? I know I could easily do this equation in Assembly.

--- Quote End ---

You're entering the hardware world. So forget everything you know about programming and assembler. Their concepts and coding style will give you poor results in HDL (if they work at all).

You need to start from scratch - learn about basic componenets (rams, registers, gates etc) and DRAW out your intended circuit on a peice of paper. Only then can you transcribe it into HDL. Verilog has a problem because it looks like C, so many people think it must be written in a similar fashion. This is a dangerous trap (as you're finding). As you're starting from scratch, you may be better off learning VHDL instead (as it is nothing like C).

I have no knowledge of the book you're talking about - but if it did work it would give very poor performance - loops like the one above unroll into sequential logic, which will give a terrible FMax (maybe 20Mhz if you're lucky). Also, floating point is rubbish in FPGAs as it requires large amounts of logic and lots of pipelining (latency). FPGAs are built to suit integer (fixed point) arithmatic. Is there any reason why you want floating and not fixed?

"direct verilog" as you put it would be perfectly suited to your application - just not with the code you've used above. I suggest using the floating point IP provided by altera.

I'd advise forgetting about floating point. FPGAs aren't designed for it. Sure, Altera provides floating point IP but you end up needing huge amounts of FPGA resources to use it unless you really know what you are doing. As others have said, you need to be thinking of designing hardware, not writing code. First analyze your problem. What are the min/max values of the inputs, outputs, and intermediate results? What precision do you need to keep in order to obtain sufficiently accurate results? What accuracy is required? How many bits are needed to represent these in binary? Then you come up with how many bits are before and after the decimal point. Prescale any inputs and intermediate constants so that no exponents are needed.

Only after all this (see a numerical methods or scientific programming book for details) will you know your fixed point format. Then do your calculations on fixed point integers. Draw out on paper where you need adders, multipliers. Learn about pipeline computing. Research parallel processing and determine if your calculation can be done in parallel. Is this a vector algorithm? If so FPGAs are particularly good at this.

Unfortunately, in spite of the marketing hype, you can't just take arbitrary algorithms and expect good results in an FPGA without learning the underlying techniques. I personally know of the existence of some of them but haven't actually implemented more than a few of these techniques.

--- Quote Start ---

I'd advise forgetting about floating point. FPGAs aren't designed for it. Sure, Altera provides floating point IP but you end up needing huge amounts of FPGA resources to use it unless you really know what you are doing. As others have said, you need to be thinking of designing hardware, not writing code. First analyze your problem.

--- Quote End ---

I think in this case is mandatory to use floating point, I need iterative divisions, divisions will bring up fractional numbers of different sizes, example. 2.9 - 2.1899, it is necessary to align exponents before make any operations, thus is necessary exponents to vary according to the input size difference, and this is exactly what floating point is about.