Building VTR in debug mode in GitPod Initialization

[sdamghan]

signed-off-by: Seyed Alireza Damghani [email protected]

Description

VTR will be compiled in debug mode in GitPod prebuilt.

Related Issue

follow up on #1766

Motivation and Context

How Has This Been Tested?

Types of changes

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

[sdamghan]

@mithro Init tasks were missed in the previous PR(#1766 ). Now the GitPod is in PR checks (end of list).
Do we have any preference for starting the project up? I only set to compile VTR in debug mode. However, we can download titan, ispd and symbiflow benchmarks as well.
@vaughnbetz I think you might have some thoughts on this as well.

[vaughnbetz]

I haven't used gitpod yet, so I don't have a very informed opinion. A few thoughts though:

From this post, it looks like it has a 30 GB disk limit, 12 GB of RAM and 7 vCPUs (which get throttled if you use them a lot). https://community.gitpod.io/t/how-much-resources-does-one-workspace-have/1677

A lot of work on the titan and ispd designs is going to be QoR work where you want cpu time measurements and fast runs, so they are less essential to get on gitpod, which won't have the cpu to do very controlled experiments. But if they'll fit in the 30 GB space limit comfortably (and I think they will) I'd pull down the Titan designs. I'd hold off on ispd for now, as we haven't integrated them into our tuning much yet.

[sdamghan]

@vaughnbetz thanks,
It seems compilation is more practical than other options; I will leave the init phase as it is now only to compile the VTR.
I am done with this PR. It is ready to merge.

[vaughnbetz]

Sounds good, thanks.