-
Notifications
You must be signed in to change notification settings - Fork 14
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
Comments
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 |
Thanks for the quick response. Find all the results folders attached |
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. |
Thanks. Here's the info you requested
|
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. 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 |
For posterity what is our version of GCC?
If we release this to people we need to give some sane range of GCC
versions.
See cacti issues, e.g.
HewlettPackard/cacti#8
Maybe we can do a pull request to cacti with some fixes.
M
…On Tue, Oct 22, 2019 at 2:12 PM Tutu Ajayi ***@***.***> wrote:
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
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2?email_source=notifications&email_token=AEFG5ACTOGFSADT6727XFG3QP47ALA5CNFSM4I2OKV6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6V4GI#issuecomment-545087001>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEFG5AG5ITU4N43ENVLIWBDQP47ALANCNFSM4I2OKV6A>
.
|
Also
HewlettPackard/cacti#6
On Tue, Oct 22, 2019 at 2:44 PM Michael Nguyen Taylor <
[email protected]> wrote:
… For posterity what is our version of GCC?
If we release this to people we need to give some sane range of GCC
versions.
See cacti issues, e.g.
HewlettPackard/cacti#8
Maybe we can do a pull request to cacti with some fixes.
M
On Tue, Oct 22, 2019 at 2:12 PM Tutu Ajayi ***@***.***>
wrote:
> 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
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#2?email_source=notifications&email_token=AEFG5ACTOGFSADT6727XFG3QP47ALA5CNFSM4I2OKV6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6V4GI#issuecomment-545087001>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEFG5AG5ITU4N43ENVLIWBDQP47ALANCNFSM4I2OKV6A>
> .
>
|
We use GCC 4.8.5 |
Okay I see. I suggest we run valgrind on cacti to find the issue.
M
…On Tue, Oct 22, 2019 at 3:18 PM Scott Davidson ***@***.***> wrote:
We use GCC 4.8.5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2?email_source=notifications&email_token=AEFG5AGF4YTA52HO5JY2KLDQP5GZVA5CNFSM4I2OKV6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB64JFQ#issuecomment-545113238>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEFG5AAGYRR4XQW7Y5WS3RLQP5GZVANCNFSM4I2OKV6A>
.
|
Hi,
The example freepdk45.cfg fails to generate for me. Specifically sram_32x32_1rw fails with the following error
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
The text was updated successfully, but these errors were encountered: