@oleg-nenashev Recently I had been busy, but can we discuss on improving the existing yosys integration as I see , a lot of people responded to it on twitter , so I can work on to make it useful to other projects.
This week is impossible for me, but we could do something on Oct 2 or 4
in that case , can i now send PR to or1k-marrochino to have yosys ( if now our jenkins work properly )
@Nancy-Chauhan AWS is kinda stable, but I still need to add a bit more resources to the instance. Good news is that I got access so that I can proceed with it
Hey guys, i looked at work you are doing. I have good knowledge of concepts related to advanced computer architecture like tomasulo's algorithm, exploiting parallelism etc. I have experience of coding in verilog for FPGA and using different synthesis tools like Xilinx, yosys(open source), i want to dive deep into new things like jenkins, docker, Kubernetes etc. Please let me know as how to start contributing into this and learn at the same time.
@akhilsingh05_twitter , It would be great if you can help me with this : we had the similar issue in other project : openrisc/mor1kx#90
@Nancy-Chauhan Hey, i have changed one thing in the code and it is working fine for me now with no error.
@Nancy-Chauhan Error was coming because yosys does not support (synopsys|synthesis) parallel_case. So, as mentioned here: https://github.com/YosysHQ/yosys/blob/master/frontends/verilog/verilog_lexer.l . Now when that type of comments are used if you see line 369 in above link it will return TOK_SYNOPSYS_PARALLEL_CASE which is unexpected thus giving error. This error can be solved if instead of comment we write it in form of attribute. I did that and error got resolved.
Yes thats true ! @akhilsingh05_twitter
But i guess we have to remove it from many files if I want to include fpu too