-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
added sed_wor option to verilate function (#40)
Co-authored-by: Anvesh Nookala <[email protected]>
- Loading branch information
Showing
1 changed file
with
53 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
21d4ab6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @nookfoo .
Isn't this already implemented in
tmrg()
function? (https://github.com/HEP-SoC/SoCMake/blob/master/cmake/tmrg/tmrg/tmrg.cmake#L171)Can you please revert the change and implement it in
tmrg
if its not there.21d4ab6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see now what you wanted. You want to keep
wor
for implementation but not for simulation.In that case I think it makes sense to create a new
sed_wor
SoCMake function, and create a target before simulation target.I don't want to overcomplicate any of the targets, and verilator target is already quite complex
21d4ab6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @Risto97, yeah that would be a more clean way to do it. We are working toward the tapeout, apologies for the forcefule merge.
Do you suggest to still revert it? Otherwise, I will make a new PR with an exracted
sed_wor
function.21d4ab6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't worry now, focus on tapeout.
I will just open an issue tonight so we can change once you have more time.
In any case I think the fact that the
tmrg
function is applying sed might not be problem for you.If the structure of triglav is mostly the same as before, your verification and implementation directories are different.
Meaning when you do implementation you configure CMake there, and there is no verilator target.
In that case you can have a variable that will affect if
tmrg
function appliessed
or not, ie. when you do implementation don't apply, when simulation apply...Something like