concoredocker.v is an identical copy of concore.v with no Docker adaptations

[GaneshPatil7517]

@pradeeban
Both concore.v and concoredocker.v are 352 lines and completely identical. Unlike the Python/C++ Docker variants (concoredocker.py, concoredocker.hpp) which modify file paths from relative ./in/./out to absolute /in//out for Docker containers, the Verilog Docker variant makes no such adjustment.

In concore.v, the paths are hardcoded as:

reg[(`INPATHLEN-2)*8-1:0] inpath =  "/in";
reg[(`OUTPATHLEN-2)*8-1:0] outpath = "/out";

These already use absolute paths, so it coincidentally works in Docker, but the INPATHLEN and OUTPATHLEN defines are set for these absolute paths and would break if someone tried to use relative ./in paths locally. The Verilog variant should either:

• Have distinct local vs Docker path configurations like Python/C++, or
• Be removed if it's truly identical, with mkconcore.py just copying concore.v for both cases.

[pradeeban]

@GaneshPatil7517 don't touch the Verilog. :D It magically works. 👯

[GaneshPatil7517]

Finally @pradeeban sir you’re online 😄 i am waiting for you only......
Thank you for clarifying
Understood since it works reliably, I won’t modify the Verilog path handling.
i raised the the 2 PR please review it.....

[GaneshPatil7517]

hey @pradeeban sir i raised some issues please give the permission for Raising the PR on it....