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

Example sram_32x32_1rw configuration fails to generate #2

Open
tajayi opened this issue Sep 25, 2019 · 9 comments
Open

Example sram_32x32_1rw configuration fails to generate #2

tajayi opened this issue Sep 25, 2019 · 9 comments
Assignees

Comments

@tajayi
Copy link

tajayi commented Sep 25, 2019

Hi,
The example freepdk45.cfg fails to generate for me. Specifically sram_32x32_1rw fails with the following error

top 3 best memory configurations are:
Memory    cap: 80 GB num_bobs: 1 bw: 533 (MHz) cost: $731.2 energy: 32.6101 (nJ) 
 {
 (0)  BoB       cap: 80 GB num_channels: 1 bw: 533 (MHz) cost: $731.2 energy: 32.6101 (nJ) 
    ==============
    (0) cap: 80 GB bw: 533 (MHz) cost: $731.2 dpc: 3 energy: 32.6101 (nJ)  DIMM:  RDIMM  low power: F [ 0(4GB) 0(8GB) 1(16GB) 2(32GB) 0(64GB) ]
    ==============

 }

=============================================

Error: y = 5.38 < minimum (14.82)
Aborting.
make: *** [run] Error 1

Also failing with similar issues are free45_1rw_d64_w7, free45_1rw_d64_w96 and free45_1rw_d512_w64 provided as examples for the bp design.

Note that sram_8x512_1rw succeeds.

Thanks

@stdavids
Copy link
Collaborator

Hey Tutu,

Thanks for the issue. I'm not able to replicate this on my end, can you attach your cfg file as well as cacti.cfg and cacti.cfg.out file that should reside in the failing SRAM's results/ directory. The error is after cacti so those files should exist.

@stdavids stdavids self-assigned this Sep 25, 2019
@tajayi
Copy link
Author

tajayi commented Sep 25, 2019

Thanks for the quick response. Find all the results folders attached
results.tar.gz

@stdavids
Copy link
Collaborator

Thanks Tutu,

So it looks like the issue is with the "aspect ratio" output of cacti. Your SRAMs have huge aspect ratios like 22x while mine are ~0.3. 22x wider than it is tall is a bit outside the normal scope so I'm not surprised the tools died :)

What OS are you running on? And what version of gcc is installed? I'd like to try and bootstrap a vm to see if I can replicate this output. I'll also give cacti a look and see if anything pops out at me but I'll likely need your help to verify if any fixes work. In the meantime, I'll send you the generated files for you to work with.

@tajayi
Copy link
Author

tajayi commented Sep 26, 2019

Thanks. Here's the info you requested

Linux  2.6.32-642.6.1.el6.x86_64 #1 SMP Thu Aug 25 12:42:19 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
gcc version 5.4.0 (GCC) 
Red Hat Enterprise Linux Server release 6.8 (Santiago)

@tajayi
Copy link
Author

tajayi commented Oct 22, 2019

This issue appears to be related to the gcc compiler (and possibly configuration of our servers). On 5.4.0, i get a really weird aspect ratio in the cacti output. I though switching to 4.4.7 fixed the issue, but it only resulted in the aspect ration from cacti being "NaN", which lead to a lot of coordinates in the lef file being set to NaN.
Another version of gcc had "Inf" as the aspect ratio.

My gut is that some variable or operator needs to be set explicitly in cacti. I was able to generate what appears to be usable using gcc 4.8.5

@taylor-bsg
Copy link
Collaborator

taylor-bsg commented Oct 22, 2019 via email

@taylor-bsg
Copy link
Collaborator

taylor-bsg commented Oct 22, 2019 via email

@stdavids
Copy link
Collaborator

We use GCC 4.8.5

@taylor-bsg
Copy link
Collaborator

taylor-bsg commented Oct 22, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants