Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

ORFS call to yosys-abc hits assertion if capacitive_load_unit isn't ff

Abierto
  • ¿Algo no está bien?
#3,011 5 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@maliberty ya está trabajando en esto.

Desde el 19/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Stale
Subject

[Flow] for any util, flow Makefile, or flow script issues.

Describe the bug

If the first Liberty file that is listed in LIB_FILES has capacitive_load_unit set to anything other than "ff", the ORFS call to yosys-abc (via yosys) fails with an assertion error that is hidden from the ORFS user.

What the ORFS user sees is:

24. Executing ABC pass (technology mapping using ABC).
24.1. Extracting gate netlist of module `\gcd' to `<abc-temp-dir>/input.blif'..
24.1.1. Executing ABC.
ERROR: ABC: execution of command ""/home/jeffng/dev/vt_ref/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys-abc" -s -f /tmp/yosys-abc-6lOhd2/abc.script 2>&1" failed: return code 134.
Command exited with non-zero status 1
Expected Behavior

yosys-abc (and more specifically abc) should be able to handle a capacitive_load_unit other than ff and scale the values accordingly for their own use.

Environment
ORFS 344623d0a158d1385a920da5dda85d157eb65386 (Jeff's branch with the mods to ASAP7 for repro)

Can also use https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/pull/3010
To Reproduce

make DESIGN_CONFIG=designs/asap7/gcd/config.mk

The contents of the abc script that gets executed and generates the assertion:

echo + read_blif "/tmp/yosys-abc-6lOhd2/input.blif";
read_blif "/tmp/yosys-abc-6lOhd2/input.blif";
echo + read_lib -X "*x1p*_ASAP7*" -X "*xp*_ASAP7*" -X "SDF*" -X "ICG*"   -w "/ho
me/jeffng/dev/vt_ref/OpenROAD-flow-scripts/flow/./objects/asap7/gcd/base/lib/mer
ged.lib" ;
read_lib -X "*x1p*_ASAP7*" -X "*xp*_ASAP7*" -X "SDF*" -X "ICG*"   -w "/home/jeff
ng/dev/vt_ref/OpenROAD-flow-scripts/flow/./objects/asap7/gcd/base/lib/merged.lib
" ;
echo + read_constr -v "/home/jeffng/dev/vt_ref/OpenROAD-flow-scripts/flow/./obje
cts/asap7/gcd/base/abc.constr";
read_constr -v "/home/jeffng/dev/vt_ref/OpenROAD-flow-scripts/flow/./objects/asa
p7/gcd/base/abc.constr";
echo + source /home/jeffng/dev/vt_ref/OpenROAD-flow-scripts/flow/scripts/abc_spe
ed.script;
source /home/jeffng/dev/vt_ref/OpenROAD-flow-scripts/flow/scripts/abc_speed.scri
pt;
echo + write_blif /tmp/yosys-abc-6lOhd2/output.blif;
write_blif /tmp/yosys-abc-6lOhd2/output.blif
Relevant log output
Screenshots

No response

Additional Context

No response

Lenguaje dominante
Verilog
Estrellas
767
Forks
544
Merge medio
2 d 3 h
PR fusionados (30 d)
96

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de The-OpenROAD-Project/OpenROAD-flow-scripts

Todos los issues de The-OpenROAD-Project/OpenROAD-flow-scripts

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.