Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nvc elaboration error when enabling branch coverage #903

Closed
tmeissner opened this issue Jun 26, 2024 · 3 comments
Closed

nvc elaboration error when enabling branch coverage #903

tmeissner opened this issue Jun 26, 2024 · 3 comments
Assignees

Comments

@tmeissner
Copy link

tmeissner commented Jun 26, 2024

I often get nvc errors during elaboration when I enable branch coverage on quite complex designs and testbenches.

$ nvc --std=19 -L ./ -e --cover=statement,expression,fsm-state,functional,branch \
        --cover-spec=Coverage.sfile axififot

*** Caught signal 11 (SEGV_MAPERR) [address=0x45, ip=0x565277bf13db] ***

[0x565277b1b835] ../src/util.c:870 signal_handler.lto_priv.0
[0x7fdd37668f8f] (/usr/lib/x86_64-linux-gnu/libc.so.6) 
[0x565277bf13db] ../src/jit/jit-irgen.c:337 j_jump.lto_priv.0
[0x565277bfb334] ../src/jit/jit-irgen.c:2177 irgen_block.lto_priv.0
[0x565277bfe59e] ../src/jit/jit-irgen.c:4234 jit_irgen
[0x565277c15606] ../src/jit/jit-llvm.c:3532 llvm_aot_compile
[0x565277bd76b1] ../src/cgen.c:276 cgen_async_work.lto_priv.0
[0x565277bd5d6d] ../src/thread.c:890 execute_task.lto_priv.0
[0x565277bd5f27] ../src/thread.c:1050 steal_task.lto_priv.0
[0x565277bd617c] ../src/thread.c:1077 worker_thread
[0x565277bd5c59] ../src/thread.c:559 thread_wrapper
[0x7fdd376b5fd3] (/usr/lib/x86_64-linux-gnu/libc.so.6) 
[0x7fdd3773581f] (/usr/lib/x86_64-linux-gnu/libc.so.6) __clone

Please report this bug at https://github.com/nickg/nvc/issues
$ nvc --version
nvc 1.13-devel (1.12.0.r89.g34e3ede2) (Using LLVM 14.0.6)
Copyright (C) 2011-2024  Nick Gasson

If I disable branch coverage the simulation runs without this error.

Maybe the error message helps, as I cannot give an MWE at the moment. The design is confidential and complex.

@Blebowski
Copy link
Contributor

Hi,
@tmeissner maybe if you reconfigure with --disable-lto, rebuild NVC and re-run, the stack-trace could give
more precise information on the place in code where the error occurs.

@nickg
Copy link
Owner

nickg commented Jun 26, 2024

Adding --enable-debug to configure might be helpful too.

@nickg
Copy link
Owner

nickg commented Jun 26, 2024

Never mind: I managed to reproduce it. I'll push a fix shortly...

@nickg nickg self-assigned this Jun 26, 2024
@nickg nickg closed this as completed in 031f4ce Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants