File: lpm.txt

package info (click to toggle)
iverilog 0.9.5-1
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 6,732 kB
  • sloc: cpp: 69,595; ansic: 39,290; yacc: 5,343; sh: 3,231; makefile: 1,174
file content (26 lines) | stat: -rw-r--r-- 1,170 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

WHAT IS LPM

LPM (Library of Parameterized Modules) is EIS-IS standard 103-A. It is
a standard library of abstract devices that are designed to be close
enough to the target hardware to be easily translated, yet abstract
enough to support a variety of target technologies without excessive
constraints. Icarus Verilog uses LPM internally to represent idealized
hardware, especially when doing target neutral synthesis.

In general, the user does not even see the LPM that Icarus Verilog
generates, because the LPM devices are translated into technology
specific devices by the final code generator or target specific
optimizers.

INTERNAL USES OF LPM

Internally, Icarus Verilog uses LPM devices to represent the design in
abstract, especially when synthesizing such functions as addition,
flip-flops, etc. The ``synth'' functor generates LPM modules when
interpreting procedural constructs. The functor generates the LPM
objects needed to replace a behavioral description, and uses
attributes to tag the devices with LPM properties.

Code generators need to understand the supported LPM devices so that
they can translate the devices into technology specific devices.