search

bespoke-silicon-group / bsg_replicant

BSG Replicant: Cosimulation and Emulation Infrastructure for HammerBlade
BSD 3-Clause "New" or "Revised" License
27 stars 21 forks source link

VCS Parsing Error #821

Closed Yuan-Mao closed 1 week ago

Yuan-Mao commented 1 year ago

The commit I am looking at: 6515c42

With VCS 2022, when compiling pod_X1Y1_ruche_X16Y8_hbm_one_pseudo_channel/bigblade-vcs/exec/simv during "make regression", I will get the following error:

Source file "tb_timescale=1ps/1ps" cannot be opened for reading due to 'No such file or directory'.

Looks like VCS thinks "tb_timescale=1ps/1ps" is a filename instead of some parameter. Not sure if it is a bug from 2022 VCS.

https://github.com/bespoke-silicon-group/bsg_replicant/blob/65a2398c3f256370f4f315bd12f6fa9c89deee3a/libraries/platforms/bigblade-vcs/link.mk#L61

taylor-bsg commented 1 year ago

Seems like you can track it down YM

On Tue, Mar 28, 2023 at 6:12 PM Yuan-Mao @.***> wrote:

The commit I am looking at: 6515c42 https://github.com/bespoke-silicon-group/bsg_replicant/commit/6515c42b03730a1f2e584d81612976a4615d0ac8

With VCS 2022, when compiling pod_X1Y1_ruche_X16Y8_hbm_one_pseudo_channel/bigblade-vcs/exec/simv during "make regression", I will get the following error:

Source file "tb_timescale=1ps/1ps" cannot be opened for reading due to 'No such file or directory'.

Looks like VCS thinks "tb_timescale=1ps/1ps" is a filename instead of some parameter. Not sure if it is a bug from 2022 VCS.

https://github.com/bespoke-silicon-group/bsg_replicant/blob/65a2398c3f256370f4f315bd12f6fa9c89deee3a/libraries/platforms/bigblade-vcs/link.mk#L61

— Reply to this email directly, view it on GitHub https://github.com/bespoke-silicon-group/bsg_replicant/issues/821, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFG5AFIBMY2EQD3AZVIS2DW6OEBTANCNFSM6AAAAAAWLJCCVE . You are receiving this because you are subscribed to this thread.Message ID: @.***>

gaozihou commented 1 month ago

It seems like the error is caused by the -L flag, removing the -L would fix everything. I could not find the -L and -M flags in the VCS user guide and the vcs -help page, and I guess these two flags might have been accidentally added?

dpetrisko commented 1 month ago

If we actually want to link, it should be -LDFLAGS "-L ..."

https://github.com/black-parrot/black-parrot/blob/08edfb479c7b5d55d665a63464785044c6b4cd35/bp_common/syn/Makefile.vcs#L40

but it looks like maybe we're trying something else there. I think one wrinkle is that was probably written for VCS-MX which may have slightly different options. I would propose we change to whatever works for a modern VCS