-
Notifications
You must be signed in to change notification settings - Fork 360
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
Crash when running UVVM Axistream VVC #2644
Comments
I can reproduce on Windows but not on Linux. I am investigating. |
You should simply increase the size of the stack by recompiling ghdl with additional flags: |
Alright, I guess this is sort of a temporary solution? |
Not so temporary. |
A workaround in UVVM to fix this issue has been released in v2 2024.07.03. |
thx! bro.
…________________________________
发件人: erick166 ***@***.***>
发送时间: 2024年7月18日 15:07
收件人: ghdl/ghdl ***@***.***>
抄送: HeLili ***@***.***>; Comment ***@***.***>
主题: Re: [ghdl/ghdl] Crash when running UVVM Axistream VVC (Issue #2644)
A workaround in UVVM to fix this issue has been released in v2 2024.07.03.
The constant C_MAX_TUSER_BITS in axistream_bfm_pkg has been reduced from 64 to 32, and moved to adaptations_pkg to be configurable by the user.
―
Reply to this email directly, view it on GitHub<#2644 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEKRAVDMAAKCKWMOTQHJOS3ZM5ST7AVCNFSM6AAAAABF4EYM26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZVG44DCNRSG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I think this has been solved in the latest UVVM release v2024.07.03b. |
Great to know!
|
Description
GHDL crashes with the following error when using the UVVM Axistream VVC:
How to reproduce?
To reproduce this error run the following testbench.
Context
Additional context
I think the problem started in the latest UVVM release when C_MAX_TUSER_BITS in axistream_bfm_pkg was changed from 8 to 64. I see that the error is gone when decreasing this constant or when decreasing for example C_VVC_CMD_DATA_MAX_BYTES in transaction_pkg. So perhaps it's too much data to handle?
The text was updated successfully, but these errors were encountered: