make issue

[jimmy-adams]

Hello, when git clone the contest resp and try making, the terminal gives the following error log:

error: cannot find symbol HttpRequest request = HttpRequest.newBuilder() ^ symbol: variable HttpRequest location: class com.xilinx.fpga24_routing_contest.CheckPhysNetlist /media/x2-b7010/data02/routing2023/fpga24_routing_contest/src/com/xilinx/fpga24_routing_contest/CheckPhysNetlist.java:131: error: cannot find symbol HttpResponse response = client.send(request, HttpResponse.BodyHandlers.ofInputStream()); ^ symbol: class HttpResponse location: class com.xilinx.fpga24_routing_contest.CheckPhysNetlist /media/x2-b7010/data02/routing2023/fpga24_routing_contest/src/com/xilinx/fpga24_routing_contest/CheckPhysNetlist.java:131: error: package HttpResponse does not exist HttpResponse response =

the OS is ubuntu 18.04 and java version is: openjdk version "11.0.19" 2023-04-18 OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1) OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)

[eddieh-xlnx]

Hi @jimmy-adams. Sorry you're having issues. Am I right in inferring that you are using Ubuntu 18.04? GitHub Actions doesn't have that image anymore, so I can't test with it.

I did try test with Temurin Java 11 though: https://github.com/Xilinx/fpga24_routing_contest/actions/runs/6774405356 and it looks like it passes.

Java 11 docs show that java.net.http.HttpRequest is a part of the standard Java library, and it seems strange that you don't get an error during import java.net.http.HttpRequest at the top of the file, nor with the HttpClient declaration a few lines above: https://github.com/Xilinx/fpga24_routing_contest/blob/718a308ba4bb8764963d91cfd2050ffbd88f41d5/src/com/xilinx/fpga24_routing_contest/CheckPhysNetlist.java#L120

If possible, can you try downloading and using a local Java runtime (e.g. https://adoptium.net/temurin/releases/) and not using the system one, and/or using a more modern version of Ubuntu? And can you show me how you got the java version output?

Thanks for working with me to get to the bottom of this!

[eddieh-xlnx]

Hi @jimmy-adams. Are you still having issues with this?

[jimmy-adams]

Hi Eddie, Thank you for your attention. I have fixed the problem by installing the java 11 version to meet the requirement. Sorry for the late reply. BTW, i want to ask more info about the routing contest. The optimization in this competition only happens inside the RWrouter package? I am still not clear how to begin with.

BEst Regards

---

发件人: eddieh-xlnx @.> 发送时间: 2023年11月22日 8:00 收件人: Xilinx/fpga24_routing_contest @.> 抄送: jimmy-adams @.>; Mention @.> 主题: Re: [Xilinx/fpga24_routing_contest] make issue (Issue #38)

Hi @jimmy-adamshttps://github.com/jimmy-adams. Are you still having issues with this?

― Reply to this email directly, view it on GitHubhttps://github.com/Xilinx/fpga24_routing_contest/issues/38#issuecomment-1821880232, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJ5KWMMJMNQA7O7IGSNQ2MTYFU6AHAVCNFSM6AAAAAA664AQDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRRHA4DAMRTGI. You are receiving this because you were mentioned.Message ID: @.***>

[eddieh-xlnx]

Great to hear you've fixed it @jimmy-adams!

BTW, i want to ask more info about the routing contest. The optimization in this competition only happens inside the RWrouter package?

Excellent question! The contest is not exclusive to improving RWRoute; RWRoute can be considered a baseline for demonstrating one possible algorithm to solve the routing problem. As long as you fulfill the scope below (taken from https://xilinx.github.io/fpga24_routing_contest/index.html#introduction):

in that you can parse an FPGA Interchange Format input and emit a legal FPGA Interchange Format output, then you can do whatever you want inside.

I am still not clear how to begin with.

One could:

• Improve RWRoute -- for example, by improving the algorithm through tuning parameters, or by improving the implementation of the existing algorithm by writing more efficient Java code, or by evolving the algorithm itself so that it is multi-threaded and can take advantage of the 32 cores that are provided.
• Adapt other open-source routers out there (e.g. nextpnr or VPR by augmenting them to read/write the FPGA Interchange Format) to see how they fare, along with improving them in the above manner.
• Roll your own custom router, with your own custom algorithms.

Lots of options!