> Hi Jose, > On 15/07/25 22:55, Jose E. Marchesi wrote: >> Hi Piyush. >> This form of the script looks generally good to me. >> May be a good time to move to the second stage of the project, which >> if >> I am not mistaken consists in creating some dejagnu infrastructure so we >> can get testsuites running the script on the test sources. > > I’m working on a draft patch to discuss the approach before fully > implementing it. Understanding how DejaGnu and the GCC testsuite work > internally took some time. I have some doubts about the best places to > make edits for certain functionalities, and I’ll detail them in the > draft patch.
Yes, it is often better to ask sooner than later. People in this list know about both dejagnu and the GCC testsuite infrastructure. >> At this point it would be good if this and future series would be >> available in some public branch somewhere until the stuff is ready to go >> in the main gcc.git repository. Do you have access to some suitable >> forge or similar? Otherwise you may want to use forge.sourceware.org. > > I’ve been using my GitHub repository: > https://github.com/PiyushRaj927/gcc to push patches, will this work? > I can keep a dedicated branch there for accepted patches. If > preferred, I can also set up a repository on forge.sourceware.org That works just fine, thanks :) I assume the branch is ebpf-compiletests. As we discussed, it would be good to have a page in the wiki to document this effort, something like https://gcc.gnu.org/wiki/BPFRunTimeTests. I can create it and point to your github repo and branch, for starters. If you create an account in the wiki then I will give you write access so you can update the page. Sounds good to you?