What is the difference between direct arithmetic computation and using MegaWizard blo

writing HDL is obviously more portable between FPGA vendors, ASICs, and doesn't require Altera specific simulation libraries

i have seen better fmax numbers using LPM functions rather than HDL - i think the LPMs are implemented at an atom level rather than being synthesized, so they are or can be pretty well optimized

in theory you should be able to get HDL to be pipelined just like the LPM but it will probably not be as simple as:

out2=a*b;

--- Quote Start ---

U means they are actually same?

--- Quote End ---

Yes. "Direct" arithmetic in behavioral HDL code is the preferred way for daily FPGA coding. Only division suggests structural (MegaFunction based) code because divider inference is rather limited.

Thanks very much. But why I ask this one in Altera Mysupport, I got the following answer, which causes me confused again:

I answer your question as below.

The Altera® integer arithmetic MegaWizard offer user the convenience of performing mathematical operations on FPGAs through parameterizable functions that are optimized for Altera device architectures.

These functions offer efficient logic synthesis and device implementation.

User can customize the megafunctions by configuring various parameters to accommodate the needs.

Altera always recommend user using the MegaWizard in order to have the optimized synthesis result.

Or put it more generally, which is better inference or instantiation.

from code readability point of view we all like inference and specially so young designers as the compact code looks more impressive. At the other extreme, some poor beginners instantiate registers, or even constants, ...etc.

I always infer registers and will never instantiate them even if I fail the exam??, I always infer isolated adders/subtractors/counters etc. And certainly constants, I don't know why vendors don't remove these dead legacy components completely from their libraries.

I used to infer multipliers but not anymore for good reasons. I avoid dividers whenever possible by using inverse multiplication.

For dedicated blocks Vendors produce richer features for their components than inference which may support fully, partially or never.

The idea of inference is supposed to be just another way to call the same component from library(usually).

As to portability across vendors, this is practical for small designs as normally you will end up with some instantiations especially so for memories.

I think it is better to redesign and have more time to be paid...this is far more important for your portability yourself.