Group3: No more counting of Literals

1 / 5

# Group3: No more counting of Literals - PowerPoint PPT Presentation

Subramanian Iyer Satrajit Chatterjee Ajit Pal Yinghua Li Pawel Kerntopf Donald Chai Dennis Wu Leyla Nazhandali Ingmar Neumann Babette Van Antwerpen Alan Mishchenko. Michael Theobald Victor Kravetz Yunjian Jiang Aiqun Cao Jordi Cortadella Jackie Rice Jean-Christoph Madre

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.

## PowerPoint Slideshow about ' Group3: No more counting of Literals' - jack

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Subramanian Iyer

Satrajit Chatterjee

Ajit Pal

Yinghua Li

Pawel Kerntopf

Donald Chai

Dennis Wu

Leyla Nazhandali

Ingmar Neumann

Babette Van Antwerpen

Alan Mishchenko

Michael Theobald

Victor Kravetz

Yunjian Jiang

Aiqun Cao

Jackie Rice

Timothy Kam

Christian Stangier

Charles Brej

Dmitri Maslov

Group3: No more counting of Literals
When/Why We Count Literals
• Multi-level combinational logic optimization
• LC is sum of literals of all nodes in network
• Different flavours of LCs
• Delay independent logic factorization
• Don’t care optimization
• Objective is to minimize LC
• Used to correlate well with circuit area
Problems
• Factorization can have negative effects on
• Delay
• Creates additional levels of logic, higher fanouts
• Area
• Can result in larger area after technology mapping (e.g. tree based mapper)
• Can increase congestion, wire length
• Power
• Logic duplication can reduce power
Problems (contd.)
• No correlation between LC and area, delay and power.
• Logic optimization happens quite late in synthesis process
• Earlier optimizations may create problems that cannot be fixed at this stage
• Blame the other guy!
Directions

1. Identify cost vectors that correlate with objective functions

• Should capture:
• Structural regularities
• Local communications
• Wire length, congestion
• Efficient to compute