Eda Toolchain Debug

Do not try to figure it out from scratch — search this skill first for existing solutions!

Scope and Boundaries

This skill records EDA toolchain issues at the IT infrastructure level, including but not limited to:

• Compiler / linker version incompatibilities
• OS library conflicts
• License configuration issues
• Inter-tool integration conflicts (e.g., VCS + Verdi)
• Environment variable configuration
• Makefile / build script tool adaptation

Out of scope: RTL syntax errors, simulation logic bugs, timing analysis methodology, and other IC design knowledge. Those belong to ip-design and other skills.

Directory Structure

eda_toolchain_debug/
├── SKILL.md                    # This file: overview + usage guide + contribution rules
└── issues/                     # Case library, organized by tool subdirectories
    ├── vcs/
    │   ├── 001_verdi_pli_lto_mismatch.md
    │   └── 002_vcs_nontty_linking.md
    ├── xrun/                   # (Reserved) Cadence Xrun issues
    ├── dc/                     # (Reserved) Synopsys Design Compiler
    ├── vivado/                 # (Reserved) Xilinx Vivado
    ├── quartus/                # (Reserved) Intel Quartus
    ├── verilator/              # (Reserved) Verilator
    └── common/                 # Cross-tool generic issues (shell env, GCC version, OS libs, etc.)
        └── 001_bash_alias_noninteractive.md

Usage

When encountering EDA tool errors

1. Search issues/<tool_name>/ in this skill for similar cases first
2. If a matching case is found, follow its solution directly
3. If not found, after resolving the issue you must add a new case record

Search tips

• Search using keywords from the error message (e.g., lto-wrapper, PIE, license)
• Search by tool name + error type (e.g., vcs linker)

Contribution Rules

When to add a new case

A new record must be added when:

1. An EDA tool reports a non-RTL-syntax error (compiler, linker, environment)
2. The resolution involves modifying compile options, environment variables, installing dependencies, or other IT operations
3. The issue is reproducible (not a one-off fluke)

How to add

1. Create a new file under issues/<tool_name>/
2. File naming: <number>_<short_description>.md, where number is the next sequential ID in that tool's directory
3. Fill in using the template below

Case template

Each case must contain these fields:

# <Short title>

## Basic Info

| Field | Value |
|-------|-------|
| Tool | <Tool name and version, e.g., VCS L-2016.06> |
| OS | <e.g., Ubuntu 22.04, CentOS 7> |
| Date Found | <YYYY-MM-DD> |
| Severity | Blocking / Workaround available / Warning only |

## Symptom

<Full error message, paste key parts verbatim>

## Root Cause Analysis

<Brief explanation of the root cause>

## Solution

<Specific resolution steps, including commands, option changes, etc.>

## Notes

<Additional info: known limitations, side effects, alternatives, etc.>

Numbering rules

• Each tool directory uses independent numbering, starting from 001
• Numbers are zero-padded to 3 digits for sorting: 001, 002, ..., 099, 100

Tool Coverage

If you encounter a tool not listed above, simply create a new subdirectory under issues/.

Known Issues Index

This index should be kept up to date as cases accumulate.

VCS

Xrun

(No records yet)

DC

(No records yet)

Common